I know I've seen this problem before and have always been able to fix the
problem. The technique I use to debug Userforms is I put a break point on
the Sub line of each of the routines in the userform by click the SUB line
and ten pressing F9.

Next I start the userform the way I normally start the userform. When the
code stops on the SUB line I press F5 to continue. The last SUB that you
reach the break point before you get your error is the routine with the
problem. I then repeat the process but instead of pressing F5 when I get to
the LAST routine I step through the code using F8.

If you get the error without getting to a break point then try adding an
initialize function to the userform and breaking on the Initilize function.
if you get an error then the Userform is corrupted. Removing items from the
userform will help isolate the problem.

I think if you build the userform again you may end up with the same problem.

"Joel" wrote:

The export file is text. You can edit the file and possible isolate where
the problem is located.

"Matt McQueen" wrote:

Joel,

Nix. Error stays the same. This was true the last time I had a similar
problem too (i.e. exporting didn't do anything). Literally the only way I
could get around it was to build the form from scratch. It's something to do
with the order in which controls are added to a form, and maybe within a
frame. Basically you need all of the controls in place before you start
writing code that controls how they affect each other. I suppose that's just
good practice... but it's frustrating since I tend to iterate quite a bit.

Cheers,

Matt

"Joel" wrote:

You could try to export the userform and then input into another workbook.

In the VBAProject window right click the userform and then export.

To import form
In the VBAProject window right click the FORMS and then import.