Help w/ The database database name needs to be repaired or isn't a database file

[dcollar]

I am managing a network that has more than a dozen users
who use a particular MS Access database the constantly
gives the error message of "The database (database name)
needs to be repaired or isn't a database file" when a
user attempts to open the database. I have checked the
users and no one is doing anything unusual. In fact
almost all users are using the database in a lookup mode
only. Maybe one or two are adding or modifying data but
thats all. Nobody's PC is locking up or doing anything
out of sorts that I can see. Users who are already in
the database can continue to use it without problems...
unless they log out of the database and then want back
in... Then THEY get the message too. The only way to
resolve the problem is to get EVERYBODY out of the
database and allow the auto-repair function operate.
Once this has been done, everybody can get back in.
Sometimes this occurs three and four times in a day. It
is causing a significant amount of distress.... Any
idea?

 

[Kevin @ 3NF]

Been there, seen that...fixed it.

Is the database split?
Does everyone have the front-end on their workstation?
Have you checked the integrity of your network (cards, cables, hubs, etc.)?
Is terminal server involved for some remote users?

 

[Tony Toews]

I am managing a network that has more than a dozen users
who use a particular MS Access database the constantly
gives the error message of "The database (database name)
needs to be repaired or isn't a database file" when a
user attempts to open the database.

Access 2000 has some problems with Win NT 4 and NT 2000 servers
commonly known as the oplocks fix. The most common problem besides
the opslock problem is intermittently flaky hardware.

Users must not use abruptly terminate Access such as by cancelling the
job using Task Manager or by powering off their system without doing a
shutdown first. IPX has also been a problem.

Ensure that all users are at the same Access SR level and Jet SP.
Preferably the latest one. (I use the various API calls available
and am checking the version number, size and date/time of a crucial
dll, MSJET35/40.DLL, to ensure it matches what I have on my system.)
See the Verify Appropriate Jet Service Pack is installed Tips page at
my website.

Thera are other causes of corruption mentioned on my website.

To retrieve your data
- make a backup copy (very important)
then try
- download and use the jetcomp fix/software appropriate for your
version of Access
- import from the corrupt mdb.
(If importing works then use the sysrels utility at the
following location to copy the table relationships layout window
http://www.trigeminal.com/lang/1033/utility.asp?ItemID=12#12)
- try opening in a newer version of access
- try using MSQuery or ODBC
- finally visit www.pksolutions.com or other repair facility as seen
in these newsgroups and as documented at my Tips page on corruption.

Peter Miller has stated that you should always import all objects in a
repaired MDB into a new MDB as there may be minor corruption still
left which can get worse over time.

For more information on corruption including a more links, official MS
KB articles and a list of vendors who state they can fix corruption
see http://www.granite.ab.ca/access/corruptmdbs.htm
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm