Whenever there is more than one person logged into a networked database we
get an icon that says we do not have exclusive excess to the database. if we
click the "OK" button 31 times the icon disappears and everythink apears OK.
If only one user is using the database we do not get this message
Can anyone please help me??
--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html
"Ian Shaw" <Ian...@discussions.microsoft.com> wrote in message
news:C95850DA-0F7F-4A19...@microsoft.com...
The second someone else enters the database the subsequent new users always
get the icon displayed requiring the new user to press enter 31 times.
I would think if many one users can enter and delete information from the
database, then the permissions would be set correctly wouldn't they??
Right-click, choose new..text file, and create a text file and save it - if
they can then they can't, then they don't have create permissions on the
folder.
If they can, can they then successfully delete this file? If they can't,
then they don't have delete permissions on the folder.
--
Joan Wild
Microsoft Access MVP
Where do I go from here??
Please help, any advice will be well received.
Many thanks,
Ian
The '31' times seems odd. Perhaps there is code in a startup form that is
triggering this?
The exact message is "You do not have exclusive access to the database at
this time. If you proceed to make changes, you may not be able to save them
later."
Help us please !!
If users are using a desktop shortcut to open the mdb, check that the
shortcut doesn't have a /excl switch in the target.
You should split the database and have just the backend (tables on the
server). Give each user a copy of the frontend (all other objects) on their
workstation. The frontend would contain linked tables (linked to the tables
in the backend on the server).
Also (just to be sure), this is happening on opening the mdb? Or is it when
they enter design view?
The solution is really quite painless. Create a new empty Access database
and import all of the old databases objects into it including if you use them
import/export specifications (see options on import).
You can then set your password, startup, etc on the new database and you are
good to go.
This is a far better solution then trying to get Microsoft to resolve the
issue.
--
Joan Wild
Microsoft Access MVP