Database is opened exclusively error

[Brandon]

Hello, I have an MDE File for use on the network that is
shared between users. I have it set so multiple people
can log in (default open mode is set to 'shared'). So why
do I get an error message that says, "You attempted to
open a database that is already opened exclusively by
user 'Admin' on machine 'xxx-EVANSR0. Try again when the
database is available."
This is an mde file, so how can he even open it
exclusively? I'm sure he doesn't even know this has
happened either as he knows nothing about MS ACCESS. Can
you help? Thanks!
Brandon

 

[Joseph Meehan]

Hello, I have an MDE File for use on the network that is
shared between users. I have it set so multiple people
can log in (default open mode is set to 'shared'). So why
do I get an error message that says, "You attempted to
open a database that is already opened exclusively by
user 'Admin' on machine 'xxx-EVANSR0. Try again when the
database is available."
This is an mde file, so how can he even open it
exclusively? I'm sure he doesn't even know this has
happened either as he knows nothing about MS ACCESS. Can
you help? Thanks!
Brandon

First fine out if he is open exclusively. I never thought of it so I
have never checked but you have a point, why would a mde need exclusive?
Maybe you can open one that way however.

However you may be able to resolve the problem by checking to see if
there is a YOURFILENAME.ldb file in the same directory as the
YOURFILENAME.mde file when not one has it open. If so delete the ldb file.

If you have not split the database so each users has their own front
end, you should do so. Not doing to causes a number of problems, including
the one your describe.

 

[Brandon]

-----Original Message-----


First fine out if he is open exclusively. I never thought of it so I
have never checked but you have a point, why would a mde need exclusive?
Maybe you can open one that way however.

However you may be able to resolve the problem by checking to see if
there is a YOURFILENAME.ldb file in the same directory as the
YOURFILENAME.mde file when not one has it open. If so delete the ldb file.

This is not the case. I made sure that the user still had
it opened on his desktop and I could not delete the ldb
file.

If you have not split the database so each users has their own front
end, you should do so. Not doing to causes a number of problems, including
the one your describe.

I have already split the database but I want to know why
this exclusive problem occurs. I know the best way is to
make each user have their own copy of the mde, but I don't
want to complicate it yet if I don't have to. Is there
any specific reason why this problem occurs that I can
mitigate by a setting or some option? Thanks for your
reply I appreciate it!
Brandon

 

[Joseph Meehan]

This is not the case. I made sure that the user still had
it opened on his desktop and I could not delete the ldb
file.

I have already split the database but I want to know why
this exclusive problem occurs.

Well it appears that you know who has it open. Have them close it and
verify that you can then open it exclusively or make the edits you want as
long as they do not have it open

Next have the open it with your watching. See if they are opening it
exclusively, or if their copy of Access as this set as the default. See
check any shortcut they are using to see if the shortcut is specifying
exclusive.

I know the best way is to
make each user have their own copy of the mde, but I don't
want to complicate it yet if I don't have to.

Trust me, you want to do it now to avoid more complications later.
Access does not like sharing without splitting.

Is there
any specific reason why this problem occurs that I can
mitigate by a setting or some option? Thanks for your
reply I appreciate it!
Brandon

Just find out why it is open exclusively and address that. It seems it
is being opened exclusively.

Note there are other possibilities, but you want to start with this one
first.

 

[Guest]

Brandon, I am having a similar issue and wanted to know some more specifics
about your situation...
My application is in Access 2002, but my data is stored on a Server that was
recently updated to Windows Server 2003. I am still using the DAO object
model.
Do you see any similarities?