ACC1x: "Object Not Found" Error When Compacting Database

 Last reviewed: July 18, 1997
Article ID: Q109367
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1

SYMPTOMS

When you are compacting a database, the error message 

   Object Not Found <Filename>.MDB
occurs. <Filename> is the name of the database file you are trying to compact.

CAUSE

The database's System tables may be corrupted, or the MSysObjects table contains a pointer to an object in one of the other System tables that no longer exists.

RESOLUTION

Try to following steps to find the cause of the error and correct the problem:

  1. Make a backup copy of the .MDB file.

  2. Open the .MDB file in Microsoft Access.

  3. Identify the corrupted object by opening every object in the database in Design view. When you try to open a corrupted object in Design view, you should receive an error message stating that the object does not exist, or that you do not have permissions to the object, even though you do.

  4. After you have identified the corrupted object, close the database and then create a new database. Import all the good tables from the original database to the new database. Compact the new database to make sure that it will compact correctly.

  5. Repeat step 4 for the queries, forms, reports, macros, and modules in the original database, excluding any corrupted objects. Make sure to compact the new database after you import each object type.

  6. In the new database, re-create any object that you identified as corrupted in the original database.

  7. In the new database, re-create any table relationships that exist in the original database.

  8. In the new database, re-create any Import/Export specifications that exist in the original database.

STATUS

This problem no longer occurs in Microsoft Access version 2.0.

REFERENCES

Microsoft Access "User's Guide," version 1.1, Chapter 4, "Importing or Attaching Objects from Microsoft Access Databases," pages 68-69, and Chapter 25, "Compacting a Database," pages 636-637

Keywords : GnlCmp kberrmsg kbusage
Version : 1.0 1.1
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : Info_Provided

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.