BUG:GPF Manipulating Microsoft Excel Spreadsheet w/OLE Control

 Last reviewed: October 3, 1996
Article ID: Q137030
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

A general protection (GP) fault at different addresses in segment 0014 occurs in EXCEL.EXE when closing the Visual Basic environment after manipulating an OLE client control that contains an embedded Microsoft Excel spreadsheet.

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 Behavior

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

  2. Add an OLE client control to the form.

  3. In the Insert Object dialog box, click Create from File, specify any valid .xls file, and click OK.

  4. Right-Click the control, and click Open. When Microsoft Excel opens, click Exit on the File menu.

  5. Right-Click the control, and click Edit. Press the ESC key to deactivate the OLE client control.

  6. Right-Click the control, and click Open.

  7. On the Visual Basic File menu, click Exit. At this point, a GP fault occurs in EXCEL.EXE at different offset addresses in segment 0014.

Additional reference words: 4.00 buglist4.00 vb4win vb4all
KBCategory: kbole 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: October 3, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.