Databse error message

  • Thread starter Thread starter Frenchy
  • Start date Start date
F

Frenchy

Second time that we have this message.

The database needs to be repaired or isn't a database file.
You or another user have unexpectedly quit micorsoft
access while a microsoft access database was open.
Do you want Microsoft Access to attempt to repair the
database?

This is a network database that people worked on entering
and modifiying data. Last time we couldn't get into the
database. It was fixed the next day, by restoring the
prior day backup and we lost some of the work. Do we have
to restore the backup again and lose the work done?

Any help is appreciated.
 
Frenchy said:
The database needs to be repaired or isn't a database file.
You or another user have unexpectedly quit micorsoft
access while a microsoft access database was open.
Do you want Microsoft Access to attempt to repair the
database?
Click to expand...

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

Another common problem is sharing the MDB containing the queries,
forms, reports, macros and modules on a server. You really want to
split the MDB. See the "Splitting your app into a front end and back
end Tips" page at my website for more info. See the "Auto FE Updater
downloads" page at my website to make this relatively painless..

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" page at my
website.

There are other causes of corruption mentioned on my website.

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
--
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
 
Back
Top