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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

The database is in an unexpected state. Microsoft Access can't open it

Status
Not open for further replies.

UzomaOk

Technical User
Nov 15, 2005
14
0
0
NG
Hi,
I need Help!!!! pls and urgently. I have an access database it got corrupted somehow but i have a backup of 6 months back. I need to get the data from the tables of the corrupt database and imort it into the backup.

When opening the corrupt database in the Access user interface, i receive the error...

"The database is in an unexpected state. Microsoft Access can't open it.
This database has been converted from a prior version of MS Access by using
the DAO compact database method instead of the convert database command on
the tools menu (database utilities sub menu). 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."
 
*** Before you do anything else, make a backup copy of the database NOW ***

Is this a FE, BE or combined database?
What is the Access version of the original database?
Are you the only user of the db?


Max Hugen
Australia
 
Its a combined database. It sits on the network and users connect to it. Its was done with 2000 Access.
 
The steps I follow to rectify a problem like this are:

1. Compact & repair.
2. If 1 fails import all objects into a new MDB file.
3. If 2 fails try JetComp.exe from 4. Restore from backup.

Ed Metcalfe.

Please do not feed the trolls.....
 
In addition to Ed's suggestions:

1. Once you fix the issue, split the FE and BE. Access has a wizard to help you with this. The majority of corruptions in Access are not with the data, but the interface objects (forms and reports) and occasionally a code module.

2. Don't even let everyone use a common FE that is stored on a server with the BE. Get each user to install it on their own pc. This may be a bit of a hassle, but it will avoid issues where one user has a later version of Access, and 'upgrades' the FE, causing problems for every other user.

Max Hugen
Australia
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top