BUG: Activating and Closing OLE Object Causes GP Fault

Last reviewed: September 17, 1996
Article ID: Q137028
The information in this article applies to:
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0
  • Microsoft Excel version 5.0

SYMPTOMS

Microsoft Excel version 5.0 generates a general protection (GP) fault in EXCEL.EXE when repeatedly activating and closing a Microsoft Excel object in a Visual Basic OLE control during run time. The offset may vary. For example, 0014:0AF7 and 0014:0B09 were reproduced in testing with the code in this article. The GP fault occurs in both 16-bit and 32-bit operating systems and applications.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Problem

  1. Start a new project in Visual Basic. Form1 is created by default.

  2. Add the following code to the Form1_Click event procedure:

       Private Sub Form_Click()
          Ole1.Close
       End Sub
    
    

  3. Add an OLE Control to Form1. When the Insert Object dialog box appears, select either a Microsoft Excel 5.0 Worksheet or Microsoft Excel 5.0 Chart.

  4. Run the program.

  5. To activate the OLE object, press the right mouse button, and click Open. Set the focus back to Form1, and execute the Form_Click event procedure.

  6. Repeat Step 5 and the GP fault occurs.


Additional reference words: 4.00 GPF vb4win vb4all buglist4.00 excel
KBCategory: kbole kbinterop kbbuglist
KBSubcategory: IAPOLE


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: September 17, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.