D'base always exclusive access ?

  • Thread starter Thread starter John Pritchard
  • Start date Start date
J

John Pritchard

I'm told that the users open by double clicking the
application icon and that tools->options->advanced tab
shows they should open in shared mode by default. The
application is very simple and I've never bothered with
security and only want to ensure they can work multiuser
again.

I'm only 3 months into Access development and this is my
first project - which was running well 'til now - please
help !

Thanks in anticipation

Other info:

1. If I open first another user can get in BUT once I log
out I can't open the d'base again unless they log out.

2. The error message is (roughly) User Admin on
machine ??? has exclusive access to the d'base at this
time.

3. I developed the application from scratch and deliver it
over a network. I have made changes via my PC and on
the 'Access' that sits on the remote server. I'd expect to
own all the objects - but no real idea how all this works
 
This is because the person which has the database open,
does not have full rights to the directory. This person
is not able to properly create or delete the .ldb file
which is associated with a database. When a database is
opened, this file is created and when closed this is
deleted. If this file is not created when a person opens
the database, it will return an error that the user has
opened the database exclusively even when they didn't. I
have run across this with our network and had to make
changes to the folder permissions. They need to be able
to Read, Write, Modify, Execute.

Craig
 
Thanks Graig I'll look into this.

Could it be file permissions too? So that if the second
person can't read the .ldb file they'd get an exclusive
access message ?

Cheers John P.
 
John,
I don't think it is the file permissions relating to
the .ldb file. This file is actually not present until
the database is opened. Once the database is closed and
everyone has permissions, this file will disappear. This
file just keeps track of users in the database for locking
purposes. If the person doesn't have read access to
the ".ldb" file, they really wouldn't have read access to
the database since the ".ldb" file is created in the same
directory as the database.

Hope this isn't too confusing.

Craig
 
Back
Top