Problem Using New Button On User Form

[EPAIII]

Environment: Windows 10, Excel/Office 2K, The workbook was created over 15 years ago, probably on an earlier version of Excel: it has worked fairly well and been revised many times over that time.

The workbook is where I keep my personal, household budget and expenses. There are sheets for each calendar year and others for other purposes, like keeping track of the charges on my individual credit cards. So when I enter a new credit card expense or convert a scheduled one to an actual credit card expense, I use a User Form which activates VBA macros to take all the steps necessary for that entry, including adding it to the appropriate sheet for that credit card. This has worked well for many years.

This situation has come up more than once when I attempt to add a new button on this or another user form for a new credit card. First I create that new button on the user form by copying one of the existing ones and changing all the appropriate entries in it's table. Then I go to the sections of the VBA code which handle that button press and add a new "else if" condition to cover the new button. I do this by copying the existing code and just changing the name of the button. Sometimes this works but other times I get an error window pop-up that says the method is not defined or something like that.

Here are the two sections of code where these changes were made:

If EntryConversionForm.MCCCB Then           ' Citi Bank MC
    CCUsed = "Citi MC"
    
    ElseIf EntryConversionForm.MCCC1V Then   ' Capital One Visa
    CCUsed = "Cap1 Visa"
    
    ElseIf EntryConversionForm.MCCAE Then   ' American Express
    CCUsed = "AmEx"
    
    ElseIf EntryConversionForm.MCCBOAV Then  ' Bank of America Visa
    CCUsed = "BOA Visa"
    
    ElseIf EntryConversionForm.MCCPAE Then   ' PAE Chase MC
    CCUsed = "PAE MC"
    
    ElseIf EntryConversionForm.MCCC1PAE Then   ' PAE Chase MC
    CCUsed = "Cap1 PAE"
    
    'ElseIf EntryConversionForm.USAAV Then   ' USAA Visa 1.5%
    'CCUsed = "USAA Visa"
    
    Else
    CCUsed = ""
    MsgBox ("Credit card selected is not included in program.  No entry will be made.")
    GoTo Done
    
End If

and

If EntryConversionForm.MCCCB Then           ' Citi Bank MC
    CCUsed = "Citi MC"
    CCEntryName = "Citi Bank MC (bt)"
    
    ElseIf EntryConversionForm.MCCC1V Then   ' Capital One Visa
    CCUsed = "Cap1 Visa"
    CCEntryName = "CapOne Visa (bt)"
    
    ElseIf EntryConversionForm.MCCAE Then   ' American Express
    CCUsed = "AmEx"
    CCEntryName = "AmEx (bt)"
    
    ElseIf EntryConversionForm.MCCBOAV Then   ' Bank of America Visa
    CCUsed = "BOA Visa"
    CCEntryName = "Bank of America xxxx (bt)"
    
    ElseIf EntryConversionForm.MCCPAE Then   ' PAE Chase MC
    CCUsed = "PAE MC"
    CCEntryName = "Chase MC/PAE (bt)"
    
    ElseIf EntryConversionForm.MCCC1PAE Then   ' Capital One PAE
    CCUsed = "CAP1 PAE"
    CCEntryName = "Cap1 PAE Visa (bt)"
    
    'ElseIf EntryConversionForm.USAAV Then   ' USAA Visa 1.5%
    'CCUsed = "USAA Visa"
    'CCEntryName = "USAA Visa (bt)"
    
    Else
    CCUsed = ""
    MsgBox ("Credit card selected is not included in program.  No entry will be made.")
    GoTo Done
    
End If

The added lines are commented out as they were not working. The macro works perfectly for all the other credit card buttons on the user form.

OK, now here is the "kicker", yesterday, when I created the new additions they did not work. Excel even crashed when I was trying to work on them. But today, while writing this post, I reactivated the new lines of code and they worked perfectly. Nothing has changed except to remove the exclamation points at the beginning of each line so that the code would be used. I made a quick test and it converted the entry perfectly: the amount of the credit card transaction was added to that sheet just as it should have been.

Can anyone tell me what is going on here? I would really love to understand the use of VBA objects better. This button is a VBA object, isn't it? Or have i committed some syntax error? And what can I do the next time to avoid this difficulty?