DOCUMENT:Q187633 12-JUN-1998 [vbwin] TITLE :BUG: Type Mismatch Referencing UserControl on Unloaded Form PRODUCT :Microsoft Visual Basic for Windows PROD/VER:WINDOWS:5.0 OPER/SYS:WINDOWS KEYWORDS: ====================================================================== --------------------------------------------------------------------- The information in this article applies to: - Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, version 5.0 --------------------------------------------------------------------- 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. RESOLUTION ========== - Load the Form before referencing the UserControl. For example: Sub Main() Load Form1 Dim ctlMyControl as UserControl1 Set ctlMyControl = Form1.UserControl11 End Sub -or- - Place the UserControl in a different project. -or- - Move the code to 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. MORE INFORMATION ================ Steps to Reproduce Behavior --------------------------- 1. Start a new Standard EXE project in Visual Basic. Form1 is created by default. 2. From the Project menu, add a UserControl to the project. 3. Close the UserControl window, and add the UserControl to Form1. 3. From the Project menu, add a Module to the project. 4. Insert the following code into Module1: Sub Main() Dim ctlMyControl as UserControl1 Set ctlMyControl = Form1.UserControl1 End Sub 5. From the Project menu, chose Project1 Properties, and change the Startup Object to SubMain. 6. Run the project, and note that you receive the "Type Mismatch" error at this point. Additional query words: kbDSupport kbDSD kbVBp500Bug kbNoKeyWord ====================================================================== Version : WINDOWS:5.0 Platform : WINDOWS Issue type : kbbug Solution Type : kbnofix ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 1998.