March 9, 2005 at 12:52 pm
This is the error we get when we try to open a MS Access database (.mdb)
"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 recovered."
Has anyone seen this before and or know how to fix the database? Since we can't get into the database we can't try the recommended fix. We tried to import the data to SQL Server 2000 and got an error that the file was already in use (even though it wasn't).
Robert
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
March 10, 2005 at 5:49 am
First step, create a copy of the problematic database file and try your initial recovery efforts on the copy - work with the original file only as a last resort, lest you make things worse in the process.
You need to create a new, empty, Access database file, and with that database open try to import the objects from the old database. This is what the error message was telling you to do "If the original database is no longer available".
[Sometimes Access' import capability can 'sneak around' file problems such as you have - but SQL Server has no such capability.]
If you are still having trouble, there are some services you can find by Googling 'Access Database Repair' that may be able to help - they will show up in the results listings and the paid ads to the right.
Good luck - I have been down this road myself!
March 10, 2005 at 10:42 am
I had one of these the other day, and this MS KB article saved me.
http://support.microsoft.com/default.aspx?scid=kb;en-us;888634
I used the RecoverCorruptDB VBA routine to recover the tables and imported them into a copy of the database restored from the previous night's backup.
Hope this helps!
-- J.Kozloski, MCDBA, MCITP
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply