XL2000: Error Using For Each...Next Statement with OLE Object Type

View products that this article applies to.

This article was previously published under Q213830

Symptoms

If you use the For Each...Next statement in a Visual Basic module in Microsoft Excel 2000, 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:

Run-time error '13':
Type mismatch

↑ Back to the top

Cause

This behavior 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

and a command on the Tools menu contains a submenu, you will receive the error message described in the "Symptoms" section of this article.

↑ Back to the top

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 professionals 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 a Microsoft Certified Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, please visit the following Microsoft Web site:

https://partner.microsoft.com/global/30000104

For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

To avoid this problem 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

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

↑ Back to the top

More information

An OLE object type is a type of object exposed by a program through Automation. Some of the types of objects that Microsoft Excel exposes through Automation include Application, File, and Sheet. In the following example, the variable MySheet is declared as Sheet type:

Dim MySheet as Sheet

↑ Back to the top

References

For more information about For Each...Next statements, in the Visual Basic Editor, click Microsoft Visual Basic Help on the Help menu, type for each...next statement in the Office Assistant or the Answer Wizard, and then click Search to view the topic.

↑ Back to the top