Sometimes the debugger don't display the actual arror, just its caller, or its callers
caller, or its callers callers caller. Or its ...

UserForm1.Show
is good enough (unless you renamed the userform something else than UserForm1). So it must
be something it the userform's Initialize or Activate code that is either wrong or calling
something wrong. Or calling something that's calling something wrong. Or ...

Those things take time to spot. It's just the way it is.

--
HTH. Best wishes Harald
Followup to newsgroup only please.

"Hilde" wrote in message
...
I am working on a new project and have created a form
which VBA named UserForm1. It appears in the object list
for VBAProject. The line
UserForm1.Show
was being executed before, but now repeatedly gives me
a 'Need Object' error.

I can't seem to get VBA to recognize the form. Any
suggestions would be gratefully received.

Thanks. You are absolutely right -- it takes time (about 3 hours) but I
did track the error down in the initialization procedure. Nice of you
to reply.


*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!