BUG: GPF in Excel After Using Excel Spreadsheet in OLE Control

 Last reviewed: September 29, 1997
Article ID: Q129838
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 Fault (GPF) occurs at different addresses in segment 0014 in EXCEL.EXE when the Visual Basic environment is closed 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 Problem

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

  2. Add an OLE client control to the form.

  3. When the Insert Object dialog appears, select Create from File. Then specify any valid .XLS file, and click OK.

  4. Using the mouse, right-click the control, select Open. When Microsoft Excel opens, choose Exit from the File menul.

  5. Using the mouse, right-click the control, select Edit. Press the ESC key to deactivate the OLE client control.

  6. Using the mouse, right-click the control, select Open.

  7. In Visual Basic, choose Exit from the File menu.

At this point, a GP fault occurs in EXCEL.EXE at different offset addresses in segment 0014. 
Keywords          : IAPOLE IAPVBA VB4ALL VB4WIN vbwin GnrlVb kbprg
Technology        : kbole kbvba
Version           : WINDOWS:4.0
Platform          : WINDOWS
Issue type        : kbbug

================================================================================

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 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.