Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error - This database is in an unexpected state

Status
Not open for further replies.

Basia

Programmer
Apr 27, 2001
64
ML
Has anyone ever received this message? When we go to open the database, it won't open and gives a message that:

"The database has been convereted from a prior version of Microsoft Access by using the DAO CompactDatabase method instead of the Convert Database cooand on the Tools menu. This has left the database in a paritally converted state."

Okay - what happened last night? It was working fine when I left and I got this message this morning when I came in. We were not updating/converting the database.

Any clues or ideas? This is the second time this has happened. What are we doing wrong...

Help...Basia
 
Hi Basia
Open Access but do not open a database. On the Tools menu go to Database Utilities, Repair database. Find your database and click on it. Not sure if this will work or what version of Access you are using but give it a shot.
Good Luck!
 
I have this same problem, but that solution is not working. I get the same message again after I select that database to repair.

Any further ideas?

Thanks! Susan M. Wagner
LAPELS
emzadi1@yahoo.com
susanw@lapels.com
 
There is a workaround posted at faq181-1005. Hope it works for you.
 
Did anyone find the permanent fix for this problem. We recently upgrade from office97 to office2000. We have couple databases in access2000 and they worked fine for about a two months and now we are facing these problems.

1) Two databases, it's coming up with "This Database is in unexpected state; Microsoft can't open it...." error. We have front end and back end database and the both resides on sever. I was reading the treads and it mention that front end should be on client. In our situation database front end changes more often sometime couple times a day and we have multiple users uses this database(fe). It's very hard to updata everybody's fe database on their machine.

2) One database, it open up the database window instead of opening swithboard form which I have setup in startup window. In this case I have to logoff every user connected to the database and do compact & repair database and then specify the switchboard form in startup window again and disable other options in startup window again. Then works fine for sometimes couple days and sometime only couple hours. Again this database has front end and back end and they both resides on the server.

In all databases front end database has link table from backend database and also link tables from Centura SQLBase database. Some other databases works fine for now.(thank God)

Any help will be appreciated.
 
Search Microsoft for a utility called JetComp - this may enable you to affect a repair on the database "in an unexpected state" if the standard Access Repair function doesn't do the trick (which it probably won't for this error message).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top