Problems with multiple users

[Les]

I have an Access DB 2K that has been placed on a W2K network and multiple
users (up to 20) have access to it. The program runs well for a time but
then new users logging on cannot access it. The program states that there is
an error and it needs to be repaired. Users (who are still able to work with
it) are then asked to exit the program, it is repaired and works well for a
while until the same problem arises. The program is only used every six
months for the one event and has worked well previously. My guess is that it
may be the log file which initiates the error.

Is someone able to suggest a possible solution to my problem?

Thanks

Les

 

[Albert D. Kallal]

You should be running a split mdb. In fact I would give each user a mde
file.

So, spit the mdb, and give each user a copy of the front end.

You also can't have users pulling the plug, hitting re-set, or ctrl-alt del.
You also can't have any users killing ms-access via the task manager. Any of
this things can cause serious problems.

However, for starters, the recommend practice is to split the mdb into two
parts. The front end part (code, forms, reports), and the back end part with
just the data tables.

Check out the following:
http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm
http://www.granite.ab.ca/access/splitapp.htm

If after splitting, you find performance drops off, then check out the
following to restore your performance:

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

Regardless, you need to split your mdb, and carry around a fly swatter to
hit any users that hits reset, or ctrl-alt del on their pc's.

Anyway...split your mdb.

 

[Les]

Thanks Albert

I believe you are right in what you say but I was reluctant to do this as it
had worked well in the past. Maybe the users are now more literate and know
the escape avenues.
Thanks for your help

Les