Select the product you need help with

XL2000: Excel Quits Unexpectedly When You Use WorkbookBeforePrint Event

Article ID: 280825 - View products that this article applies to.

This article was previously published under Q280825

SYMPTOMS

In print preview, if you click Print, click Preview in the Print dialog box, and click Print in print preview again, the system prints your workbook to the default printer, and you receive an error message (access violation) similar to the following:

The instruction at "0x00000024" referenced memory at "0x00000024". The memory could not be "read".

Back to the top | Give Feedback

CAUSE

This error message occurs when both of the following conditions are true:

Your Excel workbook contains Microsoft Visual Basic for Applications code that uses the WorkbookBeforePrint application event to stop the printing process, by setting the Cancel argument to True.
The event is triggered from print preview in Excel.

Back to the top | Give Feedback

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Office 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

276367

(http://support.microsoft.com/kb/276367/EN-US/ )

OFF2000: How to Obtain the Latest Office 2000 Service Pack

The English version of this fix should have the following file attributes or later:

   Date        Time    Version     Size       File name        Platform
   --------------------------------------------------------------------
   12/07/2000  11:23p  0.0.0.0000  1,718,956  EXCEL.msp        x86
   12/07/2000  11:50p  0.0.0.0000  4,306,000  EXCEL_Admin.msp  x86

After the hotfix is installed, the following files will have the listed attributes or later:

   Date        Time    Version     Size       File name        Platform
   --------------------------------------------------------------------
   12/07/2000  12:26a  9.0.0.4806  7,155,757  excel.exe        x86

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in Microsoft Office 2000 Service Pack 3 (SP-3).

Back to the top | Give Feedback