RobBroekhuis
Technical User
In the Excel VBA project I'm working on, I've used userforms extensively, and have seen some odd behavior while manipulating them inside VBA. As a matter of fact, I suspect that some of this behavior is causing the GPF situation that I asked about in my previous post.
The problems always arise when I add a new control to a userform, or rename an existing control. Often, the userform code editor will then not recognize the new control (i.e., not offer it as a suggestion in its dropdown lists, not correct the upper/lower-case in references to it), and running the associated code will generate an error. Leaving and re-entering Excel typically corrects the problem. Is this a common thing, something wrong with my copy of Excel (2000, running on W95), or something I am doing wrong?
The problems always arise when I add a new control to a userform, or rename an existing control. Often, the userform code editor will then not recognize the new control (i.e., not offer it as a suggestion in its dropdown lists, not correct the upper/lower-case in references to it), and running the associated code will generate an error. Leaving and re-entering Excel typically corrects the problem. Is this a common thing, something wrong with my copy of Excel (2000, running on W95), or something I am doing wrong?