Microsoft KB Archive/248970

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 09:43, 21 July 2020 by X010 (talk | contribs) (Text replacement - ">" to ">")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


ACC2000: Invalid Page Fault When You Try to View Class Module in Design View

Article ID: 248970

Article Last Modified on 11/25/2002



APPLIES TO

  • Microsoft Access 2000 Standard Edition



This article was previously published under Q248970

Advanced: Requires expert coding, interoperability, and multiuser skills.

This article applies only to a Microsoft Access database (.mdb).


SYMPTOMS

When you try to open a Visual Basic for Applications class module in Design view, you see one or more of the following behaviors:

  • Access stops responding (hangs).
  • Visual Basic for Applications opens, but the Project window is not visible even after you click Project Window on the View menu.
  • Visual Basic for Applications opens but then hangs after a few seconds.
  • You see the following error message:

    This program has performed an illegal operation and will be shut down.

    If the problem persists, contact the program vendor.

    When you click Details (on Microsoft Windows Millennium Edition, press ALT+D), you receive the following message:

    MSACCESS caused an invalid page fault in KERNEL32.DLL at 0137:bff78040.

    NOTE: The actual memory address may vary.


CAUSE

This problem can occur under the following circumstances:

  • There is a class that declares an event.
  • A change is made to a module/class that this class calls.
  • The project is recompiled and saved.
  • The project is compacted.


RESOLUTION

To resolve this problem, obtain Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a).

To obtain SR-1/SR-1a, click the article number below to view the article in the Microsoft Knowledge Base:

245025 OFF2000: How to Obtain and Install Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a)


If your database is already affected, you can clear up the corruption by exporting and then importing the problem module as detailed in the following steps:

  1. Open the database.
  2. In the Database window, click Modules, and then click New. The Visual Basic Editor starts.
  3. If the Project window is not visible, click Project Window on the View menu.
  4. In the Project window, click Class Modules. A list of the class modules appears.
  5. Right-click the problem module, and then click Remove <module name>.
  6. You are asked to export before removing the module. Click Yes.
  7. In the Export File dialog box, click the Save in box, and then click Desktop. Click Save.
  8. On the File menu of the Visual Basic Editor, click Import File
  9. In the Import File dialog box, click the file that you just exported, and then click Open.
  10. On the File menu, click Save <database name>.
  11. On the File menu, click Close and Return to Microsoft Access.
  12. Try opening the module in Design view. The module should open without error.


STATUS

Microsoft has confirmed that this is a problem in Access. This problem was corrected in Microsoft Office 2000 SR-1/SR-1a.


Additional query words: pra

Keywords: kberrmsg kbbug kbpending KB248970