XL: GP Fault Opening Workbook with Embedded Chart

• Microsoft Excel for Windows, versions 5.0, 5.0c
• Microsoft Excel for Windows NT, version 5.0
• Microsoft Excel for the Macintosh, version 5.0
• Microsoft Excel for Windows 95, version 7.0

SYMPTOMS

In Microsoft Excel for Windows, when you open a workbook with an embedded chart, if the chart is linked to a macro in another workbook, you may receive one of the following error messages:

   Microsoft Excel version 5.0 for Windows
   ---------------------------------------

   A General Protection Fault has occurred in EXCEL.EXE at 0002:0E27.

   In version 5.0c, the error occurs at the address 0002:0E2E.

   Microsoft Excel for Windows NT
   ------------------------------

   If you are using Dr. Watson for NT the following error message displays
   very briefly and the Microsoft Excel program terminates:

      An application error has occurred and an application error log
      is being generated.
      EXCEL.EXE
      Exception: access violation (c0000005), Address 3f7c8264

   Microsoft Excel version 5.0 for the Macintosh
   ---------------------------------------------

   You receive the error message

      Cannot find macro '[workbook2]'

   where '[workbook2]' is the name of the workbook that contains the module
   assigned to the chart.

WORKAROUND

To work around this problem, if you are able to open your workbook, use either of the following methods:

Method 1: Move the macro to the workbook containing the embedded chart and

          link the chart to this macro.

          To turn the chart into a picture, follow the steps below:

          a. Select the chart.

          b. Press and hold down the SHIFT key, and select the Edit menu.

          c. From the Edit menu, choose Copy Picture.

          d. Delete the current chart.

          e. From the Edit menu, choose Paste.

          NOTE: The picture of the chart will not be linked to the data.
          Therefore, if the data changes, the chart will not be updated.

STATUS

Microsoft has confirmed this to be a problem 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.