XL98: Error Running Macro That Inserts Control into UserForm

Last reviewed: February 20, 1998
Article ID: Q181466
The information in this article applies to:
  • Microsoft Excel 98 Macintosh Edition

SYMPTOMS

In Microsoft Excel 98 Macintosh Edition, when you run a Microsoft Visual Basic for Applications macro in which you dimension a variable as a UserForm control, such as a check box, a list box, a scroll bar, or an option button, you may receive the following error message:

   Run-time error '13':
   Type mismatch

CAUSE

This behavior occurs when the following conditions are true:

  • The control you are using is included in the Microsoft Forms 2.0 Object Library.

    For example, the line of code that dimensions the variable resembles any of the following examples:

          Dim X As CheckBox
          Dim Y As Label
          Dim Z As ListBox
          Dim A As OptionButton
          Dim B As ScrollBar
          Dim C As TextBox
    

        -and-
    
  • You attempt to add a control to a UserForm using a line of code similar to the following example:

          Set X = UserForm1.Controls.Add("Forms.Checkbox.1", "Name", True)
    

This behavior occurs because these controls exist in both the Microsoft Excel 8.0 Object Library, which applies to dialog sheets, and in the Microsoft Excel Forms 2.0 Object Library, which applies to UserForms.

Unless you add "MsForms." to the beginning of the data type in the Dim statement, Microsoft Excel assumes that you want to use the Microsoft Excel object type, not the type in the Microsoft Forms 2.0 Object Library. This causes a problem when you attempt to insert a control by using the Set statement.

WORKAROUND

Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web:

   http://www.microsoft.com/support/supportnet/refguide/default.asp

To work around this problem, type "MsForms." (without the quotation marks) at the beginning of the data type in the Dim statement. For example, change the examples in the "Cause" section to the following:

   Dim X As MsForms.CheckBox
   Dim Y As MsForms.Label
   Dim Z As MsForms.ListBox
   Dim A As MsForms.OptionButton
   Dim B As MsForms.ScrollBar
   Dim C As MsForms.TextBox

Then, set the variable to the control that you want to add using Visual Basic code.

STATUS

This behavior is by design of Microsoft Excel 98 Macintosh Edition.


Additional query words: XL98 forms3
Keywords : kbdta kbdtacode
Version : MACINTOSH:98
Platform : MACINTOSH
Issue type : kbprb


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.

Last reviewed: February 20, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.