The Access 7.0 database cannot be recovered after you call the CDaoWorkspace::RepairDatabase function or the or CdbDbEngine::RepairDatabase function (167906)

The information in this article applies to:

The DAO SDK, when used with:
- Microsoft Visual C++, 32-bit Editions 4.0
- Microsoft Visual C++, 32-bit Editions 4.1
- Microsoft Visual C++, 32-bit Enterprise Edition 4.2
- Microsoft Visual C++, 32-bit Professional Edition 4.2
- Microsoft Visual C++, 32-bit Enterprise Edition 5.0
- Microsoft Visual C++, 32-bit Professional Edition 5.0
- Microsoft Visual C++, 32-bit Enterprise Edition 6.0
- Microsoft Visual C++, 32-bit Professional Edition 6.0
- Microsoft Visual C++, 32-bit Learning Edition 6.0
- The Microsoft Foundation Classes (MFC)

This article was previously published under Q167906

SYMPTOMS

If you call CDaoWorkspace::RepairDatabase() or CdbDbEngine::RepairDatabase on a corrupt Access 7.0 database, it may result in a database that is so corrupt that it cannot be recovered.

NOTE: This same behavior may occur in Microsoft Access 97 with databases That are converted from Microsoft Access 7.0. If this happens, you should either:

Create a new database in Microsoft Access 97 and import all the objects from a backup copy of the Microsoft Access 7.0 database.

- or -

Use Jetcomp.exe, a stand-alone utility, to compact the database.

CAUSE

The MSysObjects system table is corrupted.

RESOLUTION

You should always call CDaoWorkspace::CompactDatabase() before calling CDaoWorkspace::RepairDatabase() on an Access 7.0 database. It is a good idea to compact, repair, and backup your database frequently.

MORE INFORMATION

Sample Code

   /* Compile options needed: none
    */ 

   // The following code will repair the database C:\DB1.MDB
   // using the MFC DAO classes
    try
    {
        CDaoWorkspace::CompactDatabase( _T( "C:\\DB1.MDB" ),
            _T( "C:\\DB2.MDB" ) );
        CDaoWorkspace::RepairDatabase( _T( "C:\\DB2.MDB" ) );
    }
    catch( CDaoException* e )
    {
        AfxMessageBox( e->m_pErrorInfo->m_strDescription );
        e->Delete();
    }

REFERENCES

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

109953 How to troubleshoot/repair damaged Jet 3.0 and prior databases

158933 Error message: <Database name> isn't an index in this table

Modification Type:	Major	Last Reviewed:	6/2/2005
Keywords:	kbtshoot kbcode kbDatabase kbprb kbprogramming KB167906 kbAudDeveloper