"The database is in an unexpected state" any ideas? 2

[lisagippe]

Hello,

I have a db that houses our payroll for nearlly 260 employees. There are only about 18 people who use it on a daily/weekly basis. The db is split, the front end is the one that is having issues. This Friday afternoon I get a phone call that it won't open, the below error is what pops up:
The database is in an unexpected state; Microsoft Access can't open it. The database has been convereted from a prior version of M. Access by using the DAO Compact Database....etc.

1. I only compact once a month. It has worked fine for this whole month, and the whole year prior.

2. The Supervisors who have access to, and use it, do not have permissions (nor do they know how) to make any changes or compact anything.

Luckily I did have backups so we have not come to a total stand still, but, I need that front end working again. There were things added to reports that were not on the backup copies.

If you have any ideas on how to get this front end working again or what may have caused the problem in the first place so I can prevent it from happening again, please let me know. Thanks!!!!

 

[boblarson]

The frontend should NOT be a single copy accessed by users on the network. If this is the case, that is why it corrupted. If a user is connected to the database and there is a network disruption, no matter how brief, it will corrupt your mdb file.

EACH user should have a copy of the frontend on their computer. Not only will that help with corruption issues, but it will help with a lot more. Plus it will help with design work as you can work on the master and then deploy the new copies when you are ready.

I have a free tool on my website that will enable your frontend for auto updating so that all you have to do is change the version numbers in two tables and it will automatically tell the user that their frontend is out of date, close it, delete the old file, copy the new one from your master location, and then reopen automatically for the user. It can be located here:

http://www.btabdevelopment.com/main/AccessTools/tabid/78/Default.aspx

Bob Larson
A2K,A2K3,A2K7,SQL Server 2000/2005,Crystal Reports 10/XI,VB6, WinXP, and Vista
Free Quick Tutorials and Samples:

http://www.btabdevelopment.com

 

[MoLaker]

boblarson is correct.

As for recovering the forms, etc. from your corrupted front-end, you might be able to import the objects into a new DB. If you still run into trouble, try importing one object at a time. It could be there is a single object shanking the whole DB. If this works up until you hit a specific object, then you can step over that object and continue importing. Perhaps you'll luck out and the corrupted object has not been updated from your backup copy.

Once you are back up and running (regardless of how you get there), you should maintain the master version of your front-end in a safe place. IT SHOULD NOT BE YOUR PRODUCTION COPY. Then each workstation should get a "copy" of the master installed locally. You might even consider making the copies an MDE instead of an editible MDB. Especially since you are dealing with a payroll DB.

 

[lisagippe]

Thank you guys so much! I will try and get it sent out to each person to have on their PC.

MoLaker, I am not able to import the tables it won't even let me choose the db as the same error pops up. Luckily my boss who looked at it last week was able to figure out that I had left all the original forms in the the back end and replaced the broken front end with the back end (which for the moment leaves me totally vulnerable but thats being worked on). I am in the process of splitting it apart now for distribution.

For anyone reading this in the future: This is a perfect example of why each user should have their own front end to work with and make a backup copy for yourself of everything whenever possible!!