new issue- trouble with "Load frmFormName"

[hoosiergoody]

So has there been a recent Excel update that would cause the vba code saying "Load frmFormName" to now cause this error:
"Run-time error '380': Could not set the List property. Invalid property value."

Using this same command worked for 2 years, and now all of the sudden it fails...

any help would be greatly appreciated!

 

[mikerickson]

What code (in the Intialize Event?) loads the list box (or combobox)?

 

[Norie]

Sounds like there's problems in the Activate/Initialize event of the userform and/or with the method you are using to populate a listbox/combobox on the form.

The first thing to do is, if there is one, to identify the line of code causing the problem.

To do that you have a couple of options.

1 Open the userform in design mode and start it by pressing F5.

2 Goto Tools>Options..., on the General tab set the error checking option to Break on all errors or Break in class modules and then try running Load frmFormName again.

 

[hoosiergoody]

from what i can tell there are multiple list boxes being used within the form. Unfortunately i didn't create this one and am trouble-shooting. No changes were done to the code or the file. The macro worked until a week ago. Excel16 is what is being used.

 

[mikerickson]

Set a breakpoint and step through the program and find out which line (probably in the userform's code module) is causing the error.

 

[hoosiergoody]

Mike- i appreciate your help...

it crashes at this command:
"Load frmCreateDisco"

I can change the form name in the properties and then the command to that new name (hence using the generic "Load frmFormName" in my explanation above).

 

[mikerickson]

Sometimes a line inside the uf code module causes an error, but when the VBEditor reactes it masks that by showing the Load (or .Show) line as the error line.
A Breakpoint plus stepping through the Intialize code reveals the true line that caused the error.

Other than that, unless we can see your Initialize code, I can't help.

 

[Norie]

If it crashes at that line it's more than likely the problem lies in the forms Activate/Initialize event code, as Mike and I suggested.

If you try what we've suggested you should be able to find the root of the problem, or at least identify which control on the form it's affecting.

 

[hoosiergoody]

Not enough coffee before i fully answered. My apologies. after stepping through, i got to this point: "Me.cboGBPDate.List = vDates"

in that picklist for the "GBPDate" list, it was past the last valid date. Therefore, not an Excel update or VBA issue.

To Mike and Norie thank you both for your replies and for your patience. Have a great day!