XL97: Page Fault Accessing Demand-Loaded Add-in (160085)



The information in this article applies to:

  • Microsoft Excel 97 for Windows

This article was previously published under Q160085

SYMPTOMS

In Microsoft Excel 97, when you run a Visual Basic for Applications macro, and then attempt to access a demand-loaded add-in, you receive an error message, and then Microsoft Excel quits.

In Microsoft Windows 95, you receive the following error message:
EXCEL caused an invalid page fault in module EXCEL.EXE at
0137:300c7df8.
In Microsoft Windows NT 3.51 or later, you receive the following error:
An application error has occurred and an application error log is being
generated.
EXCEL.exe
Exception: Access Violation (0xc0000005), Address: 0x300c7df8
NOTE: The exact address in the message may vary.

CAUSE

This problem occurs when the following conditions are true:

  • You run a Visual Basic for Applications macro during the Microsoft Excel session. -and-

  • You access a demand-loaded add-in while no workbooks are open in Microsoft Excel.

WORKAROUND

To prevent this problem from occurring, open at least one workbook or start a new workbook before you access the demand-loaded add-in.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem no longer occurs in Microsoft Excel 2000.

MORE INFORMATION

"Demand-loaded" means that an add-in is set up for use in Microsoft Excel; functionality in the add-in is available dialog boxes and menus, but the add-in file is not actually loaded into random access memory (RAM) until the functionality is requested. Demand loading an add-in requires less time than fully loading the add-in into RAM.

You may experience the problem that is described in this article when you access one of the demand-loaded add-ins in the following list:

AutoSave
Conditional Sum
File Conversion Wizard
Internet Assistant Wizard
Lookup Wizard
Report Manager
Solver
Template Wizard with Data Tracking
Web Form Wizard


Modification Type:MinorLast Reviewed:10/10/2006
Keywords:kbbug kberrmsg kbProgramming KB160085