Hi,
So, in your VBA Project, where your macro is to show frmMain, you ALSO have a UserForm that you have named frmMain? Skip,
metzgsk@voughtaircraft.com
That is correct Skip. But I'm finding out that the thing is erroring out because some of the form code is bad, not the call to the form. I just need to get my form code straight and it should fly.
Well, the only thing, I think, that would cause that kind of message, is if the form were named something else OR frmMain were defined as some other kind of object. Skip,
metzgsk@voughtaircraft.com
The only line in the macro is:
frmMain.show vbModal
After sending out the call for help I started looking closer with the debugger. I found that the control was indeed being passed to the form. I inserted an error handling function and the error is within the form_initialization procedure. I think it is odd the error showed up before the form, but that was the case. And when I chose to debug the problem the frmMain.show vbModal was highlighted so I assumed that was the error.
dsi,
The Show method for Userform DOES have, as an optional argument, vbModal or vbModeless, so THAT is not the problem. Skip,
metzgsk@voughtaircraft.com
Are you using Excel 97 ? If so vbModal has no meaning because Office 97 forms cannot be shown modelees (at least not via VBA) and so th eoption does not exist.
Just use frmMain.show , it's the ame thing anyway.
dsi,
Since I don't have a copy of 97 on my machine, I can only state that modality is an optional argument in Excel 2000. Skip,
metzgsk@voughtaircraft.com
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.