Microsoft KB Archive/172103

= XL97: Unexpected Results Using the Caller Property in a Menu =

Article ID: 172103

Article Last Modified on 11/23/2006

-

APPLIES TO


 * Microsoft Excel 97 Standard Edition

-



This article was previously published under Q172103





SYMPTOMS
When you use the Caller property in a Visual Basic for Applications macro to determine which menu item has been clicked, you may get incorrect results.



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

The Caller property for a menu item returns an array of information about that menu item. The fourth element of the array should equal zero. The following sample macro illustrates how to set the fourth element of the array to zero. This emulates the behavior of earlier versions of Microsoft Excel. Sub Run_Menu_Item z = Application.Caller z(4) = 0 For Each i In z          MsgBox i       Next End Sub



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Excel 97 for Windows, Service Release 1.

