|
Home > Archive > MS Access Multiuser > April 2005 > Users locking database somehow (Access 2.0)
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Users locking database somehow (Access 2.0)
|
|
| B. Harwood 2005-04-06, 8:06 pm |
| I have an old Access 2.0 application (don't ask) that about 20 users
in my organization work with. Till now, we have had no problem with
multiple users being in the database at the same time. However,
recently, it seems that when certain users are in the database, others
(including myself) cannot get in.
I have used the "ldb viewer" to find out who is using the application
during those times and have checked all of those machines. No one is
opening the database "exclusively", and all of the multiuser settings
in the options are set to "Shared"; however, two users seem to be able
to lock all others out.
Can anyone tell me what might possibly be enabling just certain users
to lock the database without opening it exclusively or having their
multiuser/ODBC settings set to Exclusive?
Brenda
| |
| david epsom dot com dot au 2005-04-06, 8:06 pm |
| Windows will opportunistically try to upgrade shared locks
to exclusive locks if it gets the chance. It is supposed
to back down to shared locks if a second user wants to
access the file. There may be some problem with the way
the Win16 emulation system handles this: perhaps you
could try turning off OPLOCKS at the server.
Search MS for information on opportunistic locking and
OPLOCKS registry settings.
(david)
"B. Harwood" <boriscatbobo@yahoo.ca> wrote in message
news:d0ead08b.0503161242.6b54a4f7@posting.google.com...
>I have an old Access 2.0 application (don't ask) that about 20 users
> in my organization work with. Till now, we have had no problem with
> multiple users being in the database at the same time. However,
> recently, it seems that when certain users are in the database, others
> (including myself) cannot get in.
>
> I have used the "ldb viewer" to find out who is using the application
> during those times and have checked all of those machines. No one is
> opening the database "exclusively", and all of the multiuser settings
> in the options are set to "Shared"; however, two users seem to be able
> to lock all others out.
>
> Can anyone tell me what might possibly be enabling just certain users
> to lock the database without opening it exclusively or having their
> multiuser/ODBC settings set to Exclusive?
>
> Brenda
|
|
|
|
|