J
Jane
We have an Access 2003 application loaded on our office workstations. The
application has a front end on the workstation and the back end on a server.
It is loaded on a folder on the c: drive (not a shared folder).
One workstation is used by several people. Each person has their own user
login on this machine. When one person is logged in and is using the
database, and another person jumps on the computer, logging in under their
own user account, they foul everything up by trying to open the database. We
get the message 'Database is locked' and the only way to solve the problem is
to log in as administrator and copy a fresh version of the database.
I don't like that people are doing this but it happens. Is there a setup or
configuration that I don't know about, or a way to prevent this from
happening?
application has a front end on the workstation and the back end on a server.
It is loaded on a folder on the c: drive (not a shared folder).
One workstation is used by several people. Each person has their own user
login on this machine. When one person is logged in and is using the
database, and another person jumps on the computer, logging in under their
own user account, they foul everything up by trying to open the database. We
get the message 'Database is locked' and the only way to solve the problem is
to log in as administrator and copy a fresh version of the database.
I don't like that people are doing this but it happens. Is there a setup or
configuration that I don't know about, or a way to prevent this from
happening?