XL98: Run-time Error Using For Each Loop with OLE Object Type (192279)
The information in this article applies to:
- Microsoft Excel 98 Macintosh Edition
This article was previously published under Q192279 SYMPTOMS
If you use the For Each...Next statement in a Visual Basic for Applications
macro, and you declare the variable used to iterate through the elements of
the collection as an OLE object type, such as MenuItem, you may receive the
following error message when you run the macro
procedure:
Run-time error '13':
Type mismatch
CAUSE
This problem occurs only if an error is encountered while the objects are
being retrieved from the collection. This problem may occur with object
types that include MenuItem, Sheet, and DrawingObject.
For example, if you run the following procedure
Sub Show_Menu_Items()
Dim m as MenuItem
For Each m In Activemenubar.Menus("Tools").MenuItems
MsgBox m.Caption
Next
End Sub
you will receive the error message described in the "Symptoms" section of
this article.
WORKAROUNDMicrosoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to 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 requirements.
To avoid receiving an error message when you use the For Each...Next
statement in a Visual Basic module, declare the variable used to
iterate through the elements of the collection as Variant type, or
Object type instead of as an OLE object type as in the following
example:
Sub Show_Menu_Items()
Dim m as Object
For Each m In ActiveMenuBar.Menus("Tools").MenuItems
MsgBox m.Caption
Next
End Sub
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 6/17/2005 |
---|
Keywords: | kbbug kbdtacode kberrmsg kbnofix KB192279 |
---|
|