Microsoft Access quits when you add data through a query after you upgrade to Microsoft Jet 4.0 Service Pack 5 (309163)


The information in this article applies to:

  • Microsoft Office Access 2003
  • Microsoft Access 2002
This article was previously published under Q309163
For a Microsoft Access 2000 version of this article, see 304084.

Novice: Requires knowledge of the user interface on single-user computers.

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

SYMPTOMS

When you try to add a record to a datasheet that is produced by a query that has three or more tables, Microsoft Access will either stop responding (hang) briefly and will eventually quit without a warning or error, or you receive one of the following error messages, and then Access quits:

Error message 1

MSACCESS caused an invalid page fault in module MSJET40.DLL

Error message 2

An application error has occurred and an application log is being generated. MsAccess.exe

Error message 3

Msaccess.exe has generated errors and will be closed by Windows. You will need to restart the program.

NOTE: The file names in these three error messages may be something other than "MsAccess.exe."

Error message 4

Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience.

Error message 5

Msaccess has caused an error in
MSJET40.DLL.
Msaccess will now close.

If you continue to experience problems, try restarting your computer.

RESOLUTION

This problem was fixed in Microsoft Jet 4.0 Service Pack 6 (SP6) and later.

For additional information about how to obtain the latest Jet 4.0 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

239114 How To: Obtain the Latest Service Pack for the Microsoft Jet 4.0 Database Engine

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 fixed in Jet 4.0 Service Pack 6 (SP6).

MORE INFORMATION

This behavior has been confirmed to occur with the following file versions of Msjet40.dll: 
   File name     Version      Size               
   ---------------------------------------
   Msjet40.dll   4.0.4431.1   1,503,504 bytes
   Msjet40.dll   4.0.4431.3   1,503,504 bytes

Steps to Reproduce the Behavior

WARNING: If you follow these steps, a general protection fault will occur on your computer. Make sure that you save and then close any open work on your computer before you follow these steps.

  1. Create a new Access database.
  2. Create the following table in Design view:
       Table: Table1
   ----------------------------
   Field Name: Ticket_ID
   Data Type: AutoNumber
   Indexed: Yes (No Duplicates)

   Field Name: TicketDate
   Data Type: Date/Time

   Table Properties: Table1
   ------------------------
   PrimaryKey: Ticket_ID
  3. Save and then close the table.
  4. Create the following table in Design view:
       Table: Table2
   ---------------------------------
   Field Name: TicketNumberID
   Data Type: AutoNumber
   Indexed: Yes (No Duplicates)

   Field Name: Ticket_ID
   Data Type: Number
   Indexed: Yes (Duplicates OK)

   Field Name:  TicketItemsDesription
   Data Type:  Text

   Table Properties: Table2
   --------------------------
   PrimaryKey: TicketNumberID
  5. Save and then close the table.
  6. Create the following table in Design view:
       Table: Table3
   ------------------------------
   Field Name: TicketItems_ID_Loc
   Data Type: Number
   Indexed: Yes (No Duplicates)

   Field Name: TicketItems_Location
   Data Type: Text

   Table Properties: Table3
   ------------------------------
   PrimaryKey: TicketItems_ID_Loc
  7. Save and then close the table.
  8. On the Tools menu, click Relationships. Add Table1, Table2, and Table3 to the Relationships window, and then click Close.
  9. Click the Ticket_ID field in the Table1 table, and then drag it to the Ticket_ID field in the Table2 table.
  10. In the Edit Relationships window, select the Enforce Referential Integrity, Cascade Update Related Fields and Cascade Delete Related Records check boxes.
  11. Click Create to close the Edit Relationships window.
  12. Click the TicketNumberID field in the Table2 table, and then drag it to the TicketItems_ID_Loc field in the Table3 table.
  13. In the Edit Relationships window, select the Enforce Referential Integrity, Cascade Update Related Fields, and Cascade Delete Related Record options check boxes.
  14. Click the Join Type button in the Edit Relationships window, and then click join type 2 in the Join Properties window.
  15. Click OK in the Join Properties window, and then click Create in the Edit Relationships window.
  16. Close the Relationships window, and then save the changes.
  17. Create the following query in Design view:
       Query: MyTables
   ------------------------------
   Type: Select Query

   Field: Ticket_ID
   Table: Table1

   Field: TicketDate
   Table: Table1

   Field: TicketNumberID
   Table: Table2

   Field: Ticket_ID
   Table: Table2

   Field: TicketItemsDescription
   Table: Table2

   Field: TicketItems_ID_Loc
   Table: Table3

   Field: TicketItems_Locations
   Table: Table3
  18. Run the MyTables query.
  19. Try to add a new record in the datasheet. After you add data to the first field from the Table2 table and try to move to the next field, note that you receive one of the errors that is mentioned in the "Symptoms" section of this article.
Modification Type:MinorLast Reviewed:7/28/2006
Keywords:kbstoprespond kbbug kberrmsg kbfix KB309163
©2004 Microsoft Corporation. All rights reserved.