Database periodically needs rebuild and locks users out

We have two MS Access 2000 databases, the Primary Database
and the Distribution Database, linked together. The
databases are saved on a Windows NT 4.0 server and users
access them through the shortcuts created when you
implement user level security. Both databases are secured
and users must log in. There are about 20 users who share
the databases.

Periodically, we will have weeks where the
databases 'crash' a number of times per day. The error
message we receive is:

"The database 'S:\Databases\Primary Database.mdb' needs to
be repaired or isn't a database file.
You or another user may have unexpectedly quit Microsoft
Access while a Microsoft Access database was open. Do you
want Microsoft Access to attempt to repair the database?"

To fix the problem, we have to rebuild the database by
logging in under the user's name that 'crashed' it, on the
computer they were using. All users must be logged out of
the databases in order for the rebuild to work. If you
are in the databases when they 'crash' you can keep using
them and the information you enter is saved; but if you
log out, you are not able to sign back in. The 'Primary
Database' is the database that has the problems and is the
database you must repair. The 'Distribution Database'
contains linked tables from the Primary Database, but
the 'Primary Database' is the database that must be
repaired. The Distribution Database does not function if
the Primary Database has 'crashed'.

Almost all of the workstations and user id's have caused
the databases to 'crash' at one point or another.

All workstations accessing the databases have the latest
critical updates from Microsoft for Office 2000
Professional and Windows 2000 Professional. All
workstations have the latest MS Jet 4.0 updates. All
workstations run Windows 2000 Professional.

We have read and implemented most of the items listed
under 'Methods That Can Be Used to Prevent Corruption'
in 'Microsoft Knowledge Base Article - 209137 ' but have
not seen a change in the frequency of this problem. Is
there anything else we can do to prevent this problem from
occurring?

Thanks,
Eric

I assume that you distribute a front end to each pc. That means that you do
NOT allow multiple users into the front end.

Further, the above means that you install the software on EACH WORKSTATION.

Further, you SHOULD be distributing a mde to each station.

the above usually fixes about 99% of your problems. Further, if one
workstation does have a problem, then all others will continue to function
normally.

So, you can continue to share the data file and the workgroup file on the
server, but the "software" side of the application must be installed on each
workstation (in fact, virtually every other piece of software you have
operates this way anyway).

You can read about fixing corruptions here, but below will state to do the
above:

http://www.granite.ab.ca/access/corruptmdbs.htm

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada

http://www.attcanada.net/~kallal.msn

I assume that you distribute a front end to each pc. That means that you do
NOT allow multiple users into the front end.

Further, the above means that you install the software on EACH WORKSTATION.

Further, you SHOULD be distributing a mde to each station.

the above usually fixes about 99% of your problems. Further, if one
workstation does have a problem, then all others will continue to function
normally.

So, you can continue to share the data file and the workgroup file on the
server, but the "software" side of the application must be installed on each
workstation (in fact, virtually every other piece of software you have
operates this way anyway).

You can read about fixing corruptions here, but below will state to do the
above:

http://www.granite.ab.ca/access/corruptmdbs.htm

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada

http://www.attcanada.net/~kallal.msn