Discussion Locked

Microsoft Access 2000 - Unexpected State

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This question is regarding an Access 2000 db running as single copy in shared mode. The db went into this state, and now it is unaccessible. Following is the exact message box text:
"This database is in an unexpected state; Microsoft Access can't open it.
This database has been converted from a prior version of Microsoft Access by using the DAO CompactDatabase method instead of the Convert Database command on the Tools menu (Database Utilities submenu). This has left the database in a partially converted state.
If you have a copy of the database in its original format, use the Convert Database command on the Tools menu (Database Utilities submenu) to convert it. If the original database is no longer available, create a new database and import your tables and queries to preserve your data. Your other database objects can't be recoverd."
P.S.: This database has been designed & running with Access 2000, and as to my knowledge, it has not been gone through any conversion. Also, as themessage points out, I can not import the tables & queries in to a new database!
If any one has any clue, I would really appreciate any help I can get, thank you.

5 replies

by peter ritchie

I'll assume that asking you to use your backup would cause the response "There is none".

Have you tried repairing the database without opening it? Run Access, don't open or create a DB and select Tools\Database Utilities\Repair database. Enter the filename of the database and press "Repair".

Check to see if there is an LDB file in the same directory as the mdb file. If there is, Access thinks someone is logged into the database--this may cause problems if no one is. You could try deleting this ldb file and re-open the mdb file.

Otherwise, you might have to contact Microsoft. You have two no-charge support requests avaialable with Access 2000 (http://support.microsoft.com/directory/onlinesr.asp)

by rocky patel

Thanks, Peter for your answer; however I've tried all those possibilities, none seemed to help. As far as backup is concerned, I do have one; but the backup file is about six days (4 business days) old. I did manage to access the file using an ODBC connection, and recover the data.

Thank you for time and efforts.

by donq

Re-open your .mdb file with the version that created the thing. Compact and repair THEN save to disk. Open Access 2000 and CONVERT the file into Access 2000. 2000 uses both ADO and/od DOA - VB engines.

by rocky patel

Thank you for your answer; however I would like to point out that this file was created in Access 2000, it had been working fine - at least since January 2001 - without any problems. I did recover all the data by opening file and importing the tables into a SQL Server database using an ODBC connection.

What I'm interested in now is to find out what caused this problem, since - as I mentioned - the database file was created using Access 2000 around September 2000, and had been working fine since. The file was never exposed to any other versions of Access!

Thanks again.

This discussion is closed to new replies.