Error 3011 Database corrupt

[danny123]

Hi there,

when i am tryint to access my Access database its giving this error:

The Microsoft Jet database engine could not find the object MSysDB. Make sure the object exists and that you spell its name and the path name correctly. (Error 3011)

I am not even able to get in there

Please Advice
Danny

[Rabbie]

I see you had a similar problem in March ( http://www.access-programmers.co.uk/...d.php?t=125633 ). Do you have a recent backup you can use?

Also check the path to your database and make sure the .mdb file is still there.

[danny123]

yeah i have the last days back up i was just curious if i cud fix this itself.

[RuralGuy]

Danny, have you seen this link by MVP Allen Browne?

[danny123]

yeah i have seen ....bu that post is my own...and tht time it was different scenareo. I was able to get into database. But this time i was not even able to open the database.
for now i have restored the backup from last night and its working fine.

Thanks for all your support!!!
Danny

[boblarson]

Originally Posted by danny123

yeah i have seen ....bu that post is my own...and tht time it was different scenareo. I was able to get into database. But this time i was not even able to open the database.
for now i have restored the backup from last night and its working fine.

Thanks for all your support!!!
Danny

One big question to ask is WHY is it getting corrupted? Some questions that might help answer that one:

1. Is it on a network?

2. Is it a single mdb file, or a front-end / back-end split?

3. Is anyone connecting to it via a wireless network connection?

4. Do you compact and repair regularly?

If you can answer those questions, it might help track down some methods that might help lessen the chances of corruption.

[danny123]

Thankyou so much for your support!
Here are the answers for the question:
1.Yes its on Network
2. It have one single mdb file (not split)
3.yeah lots of people connect it via wireless
4.No we dont generally compact and repair . We do it if something is broke down.

Thanks
Danny

[RuralGuy]

Danny,
As Bob and the link to Allen Browne's site suggests, you basically have the perfect formula for corruption. It will continue until you make the changes suggested.

[boblarson]

Yes, this is a MUST if you are to avoid corruption:

1. Split your Database to a front-end/back-end.
2. EACH USER must have their own copy of a front-end. If you don't want to touch each computer for a front-end, check out my tool for enabling front-end auto-updating here:
http://www.access-programmers.co.uk/...d.php?t=111132

3. Since users are connecting via wireless it is IMPERATIVE, not optional, but IMPERATIVE that you do the FE/BE split and have each user have their own copy. If they lose a connection, however briefly, corruption is assured. If that happens for them with the FE/BE split and they have their own FE, then damage is minimal as you just need to replace their FE.