Error 3011 - Cannot Find Object

[Guest]

Access 2002

I have a database that is currently shared by approx 5 users (front end has
NOT been split from the back end). The database sits on a shared server and
the users can access it at anytime. Record level locking has been selected.

The database has crashed twice in the past week, causing ERROR 3011 to
appear. The error message reads the following: "The Microsoft Jet database
engine could not find the object 'Databases'. Make sure the object exists and
that you spell its name and the parth name correctly."

I would like to find out two things. First, can someone explain in more
detail what this error message means. Second, does anyone know what causes
this issue?

Thanks for the help.

 

[Allen Browne]

The message indicates that the mdb file is corrupt. A pointer has gone AWOL.

For suggestions on how to prevent this from happening, see:
Preventing Corruption
at:
http://members.iinet.net.au/~allenbrowne/ser-25.html

 

[Guest]

Allen, thanks for your help.

For a little more clarification. Can the following situation cause the error?
- Two users are updating records in Table A
- User 1 has completed making updates and closes the table
- User 2 is still in the process of making updates

Will splitting the database resolve this issue?

 

[Allen Browne]

Entering data should not cause a corruption, unless there is already an
incipient corruption caused by something else such as Name AutoCorrect.

 

[Guest]

Can you please expand on how the Name Autocorrect could cause such an error?

 

[Allen Browne]

There are literally more than a dozen bugs associated with Name AutoCorrect,
including crashes that cause the database to corrupt and thoroughly
confusing Access so that it things one object is another and therefore makes
the wrong associations.

Details in:
Failures caused by Name Auto-Correct
at:
http://members.iinet.net.au/~allenbrowne/bug-03.html

 

[Guest]

Thanks Allen once again for your help.

There are literally more than a dozen bugs associated with Name AutoCorrect,
including crashes that cause the database to corrupt and thoroughly
confusing Access so that it things one object is another and therefore makes
the wrong associations.

Details in:
Failures caused by Name Auto-Correct
at:
http://members.iinet.net.au/~allenbrowne/bug-03.html