ACC2000: Running a Delete Query or Clicking Select All Records and Then Clicking Delete May Not Delete All Records

ID: Q241969


The information in this article applies to:
  • Microsoft Access 2000

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

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


SYMPTOMS

When you run a delete query, or when you open a table in Datasheet view, click Select All Records on the Edit menu, and then click Delete on the Edit menu, you may receive the following message:

You won't be able to undo this delete operation. The undo command won't be available because this operation is too large, or there isn't enough free memory. Do you want to delete these items?
When you click Yes, all records may not be deleted from the table.


STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.


MORE INFORMATION

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

Steps to Reproduce Behavior

  1. Make a copy of the Order Details table in the sample database Northwind.mdb. Be sure to copy structure and data. Name the new table Order Details Copy. Remove the primary key from the table to allow the append query to run successfully. There are 2,155 records in the Order Details table in the original Northwind.mdb file.


  2. Create an append query and run it two times to append a total of 4,310 records to Order Details Copy table. At this point there should be a total of 6,465 records in the new table.


  3. WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

    For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

    NOTE: Before you complete the next step, make a note of the current value in the MaxLocksPerFile key before you change the value so that you can restore the initial value at the end of these steps.

    Set the value in the following registry key
    HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\Jet 4.0\MaxLocksPerFile
    to a decimal value of 5,000.

    IMPORTANT: You must restart Microsoft Access after making this change.


  4. Open the Order Details Copy table in Datasheet view, hold down the CTRL key and press the A key to select all the records, and then click Delete.

    The behavior described in this article occurs only when you see the "You won't be able to undo this delete operation" warning. When prompted with this warning, click Yes.


  5. You are prompted with the following message:
    Do you want to suppress further error messages.
    Click either Yes or No; it won't change the results.

    With these actions, you would expect all records to be deleted from the table. When the delete operation is completed, however, the table still has one or more records remaining. As you lower the value for MaxLocksPerFile, the number of records remaining in the table is increased.


  6. Set the value in the following registry key
    HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\Jet 4.0\MaxLocksPerFile
    back to the value that you noted in step 3.


Additional query words: pra remain remains CTRL+A not all removed gone still there won't remove left

Keywords : kbdta
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbbug


Last Reviewed: January 18, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.