BUG: Type Mismatch Referencing UserControl on Unloaded Form
Article ID: 187633
Article Last Modified on 5/13/2003
APPLIES TO
- Microsoft Visual Basic 5.0 Learning Edition
- Microsoft Visual Basic 6.0 Learning Edition
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 6.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
- Microsoft Visual Basic 6.0 Enterprise Edition
This article was previously published under Q187633
SYMPTOMS
If you attempt to set an object variable referencing a UserControl on an
unloaded form, and the UserControl resides in the same project as the
Module containing the declaration, a TypeMismatch error occurs. This
problem does not occur if the form is loaded, if the UserControl is in a
different project, or if the code is placed in the Load Event of the Form
containing the UserControl.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products
listed at the beginning of this article. We are researching this
bug and will post new information here in the Microsoft Knowledge
Base as it becomes available.
Additional query words: kbDSupport kbDSD kbVBp500Bug kbNoKeyWord kbVBp600bug
Keywords: kbbug KB187633