Trying to open DB with Exclusive Rights

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a secured db that uses a front end client that requires the user to
login into the db.

My problem is ....I have a user whenever he tries to login into the db using
the client he gets the "You do not have exclusive access to the database at
this time. ...." warning message. The problem is he is not trying to login
into the db excusively. I have looked at user permissions and the open
exclusive check box is UNCHECK, which is correct. I have also looked at
TOOLS->OPTION->ADVANCE TAB and the Default open mode option is set on Shared.
Is there any other places that Access or Windows XP SP1 uses to open a DB in
exclusive mode. I believe that it is isolated to his machine because I am
able to logon using his userid on another machine without a problem.

Thanks in advance!!
Happy Holidays!
 
Make sure that he has full create/read/write/update/delete permisions
to the folder where the front end lives (which is presumeably on his
PC), and the folder where the common back-end lives. This is Windows
permissions, not Access ones.

HTH,
TC
 
ftrujillo,

I have a client with a similar problem - perhaps the cause is related.

Whenever they try and open their networked A02 database by double-clicking
their desktop shortcut, or by double-clicking the database file, Access will
open, but when a second user tries to open the database (by double-clicking
the shortcut or the file) it gives them an error message that they don't have
exclusive lock on the database and can't open in design view - it seems to
think the second person opening is trying to open an object in design view -
which they are NOT as the start up code is simply to open a form. HOWEVER,
if you open Access and THEN open the database (i.e. not double-clicking a
shortcut or file) it works fine!!! As many users as they want can open and
share the database!!!! I cannot replicate the problem on my system - it is
only theirs where it occurs. Again, it seems to be related to the way the
file is opened (i.e. problem occurs when double-clicking a shortcut to the
file or the file itself - it does NOT occur when opening Access first).

Did you have any lucking figuring your problem out??
 
Back
Top