Corrupted Access Database

M

Max Yaffe

Dear Group,

We've encountered a problem with an Access 2000 database we've used
for several years. Something happened to it that causes the following
error on opening:

"This database has been converted from a prior version of Microsoft
Office Access by using the DAO CompantDatabase method instead of the
Convert Database command on the Tools menu (Database Utilities
submenu). This has left the database in a partially converted state.
...."

The error goes on to say try creating a new database and import the
tables. That doesn't work either and generates the same message.

No one owns up to trying to convert the database so I'm not sure how
the error happened.

Is there anything I can do to recover this guy? Does anyone know what
might have caused this error. We do have a previous night's backup
but it still like to recover the last day's work.

Thanks
Max
 
A

Allen Browne

The message indicates that there is a corruption associated with a
compilation error.

Try this sequence:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, and reference ambiguities are
resolved.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html
 
M

Max Yaffe

Thanks for the tips Allen. We'll do them and how this doesn't happen
again. Also, I think we'll move from Access 2000 to Access 2003
company-wide.

And thanks for the great website & your clear tips.
Max
 
Top