OFF97: Resetting Project with Watch on Me Causes Crash

Last reviewed: August 12, 1997
Article ID: Q172614
The information in this article applies to:
  • Microsoft Visual Basic for Applications included with: - Microsoft Office 97 for Windows

SYMPTOMS

If you add a watch for the Me keyword in a document project and you attempt to reset the project while in debug mode, one of the following error messages appears.

Microsoft Windows 95

   The program has performed an illegal instruction and will be
   terminated.

Microsoft Windows NT

   Excel.exe - Application Error
   The instruction at "0x0014011" referenced memory at "0x15609100."
   The memory could not be "written."
   Click OK to terminate the Application.

CAUSE

This problem occurs when the following conditions are true:

  • In the Visual Basic Editor, you set a watch on the Me keyword in a document project item.

    -and-

  • The Visual Basic Editor is in debug mode.

    -and-

  • You attempt to reset the project.

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

It is not necessary to place a watch on the Me keyword in an item in a document project. The Me keyword is used in class modules to distinguish between different instances of a class. You do not need to use the Me keyword to distinguish between different items in a document project because the items are not created dynamically and they are each identified by an unique name.

Keywords          : xlvbainfo DBugDebugW kberrmsg kbprg
Version           : WINDOWS:97
Platform          : WINDOWS
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: August 12, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.