Hi,

Hope someone recognises the problem I am having and for the sake of my
sanity is able to give an opinion or better still a solution. My apologies
for the amount of information I am listing but I don't have the expertise to
identify what may be significant and what is not significant.

-I have a simple Access 2000 database which has been in use for 3 years with
only infrequent instances of the problem I will describe.
-The database is around 70mB; consists of only a handful of tables, forms,
reports and queries.
-Database is held on our server; users access the database from stand-alone
PC's. On average 3 users are using the database at any given time, this can
rise to a maximum of 8. All users input data to update tables but do not edit
any structures.
-Cabling is CAT 5.
-The database has not been replicated.
-The database has not been split into a back and front end.
-Default open mode has been set to Shared.
-Default record locking has been set to No Locks.
-Open databases using record-level locking has not been checked.
-Enable DDE refresh has been checked.
-User-Level security has not been activated; all users have full "Admin"
permissions.
-The database is backed-up automatically to streamer tape every 2 hours
using Veritas v9.
-Over the past three days we have had continual problems when users try to
open the database; this message appears "The database G:\mydatabasename.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?" A
number of users are already using the database when this message appears - it
only appears when an additional user attempts to use the database.
-When we click on Yes to repair we get the following message "You attempted
to open a database that is already opened exclusively by user "Admin" on
machine "MachineNumber". Try again when the database is available" If all
users exit the database then the database can be repaired but the problem
always recurs after a short period of time.
-By a process of elimination we have established that it is not the absence
or presence of one particular user in the database that causes this message
to appear nor does it only appear after a certain total number of users are
using the database.

Can anyone help me understand why we are getting these messages and what
action should be taken to sort it out.

TIA