Error After Reinstall

A

Anne

I had to reformat the hard drive on my laptop and reinstall everything. When
I open my main database, I get the following error:
The database is in an unexpected state. MSAccess can't open it. The database
has been converted from a prior version of Access by using DAO compact
database method instead of the convert Database command on the tools menu.
It instructs to import everything into a new database.

I did not convert the database. After the message, I can open the database
from the file menu.
Can anyone tell me what happend here?
Anne
 
A

Anne

Now, I have created a new database and imported all queries, forms and
reports. I get the same error.
Help!!!!
Anne
 
G

GVaught

Apparently the database got corrupted before you had to reformat your hard
drive. If the Access version is 2000, create an empty database and import
only the tables first. If all goes well import all the queries. If all goes
well import the forms. After the forms go into your code editor window and
immediate issue a Debug | compile. If all goes well import all your reports,
do the same Debug | compile. Continue the process until the remaining files
from your database is complete. Do one final Debug | Compile to ensure the
whole database compiles.
Return to the database window and execute a Compact/Repair on the database.

Hopefully, from that point everything is okay.

If the database is 97 import everything at once and issue the Debug |
Compile and then Repair then Compact. Over 2000 you may have to follow the
instructions for 2000 even though the problem was claimed to be fixed in
subsequent updates.
 
A

Anne

Thank you for trying to help.
This database was created in Access 2002 as Access 2000 because my clients
were using access 2000 on some of their computers. When I upgraded to Access
2003, I never converted the database, I kept it as Access 2000 format.
I did actually go and import everything into a new database and did all the
steps you describe. It still gave me the same error.
Searching the Microsoft Knowledgebase turned up nothing using several parts
of the error message, but after searching and searching I finally found the
problem in the knowledgebase as a known Microsoft error, which was fixed in
SP1. I installed office SP1 and initially still got the error even after
rebooting. But the next day the problem disappeared. I am now able to use
the old database, just the way it was.
Anne
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top