Re: Help - Shared MDE - Exclusive Access message box

"Suraj" <Suraj@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A312379C-517C-428F-8322-09CD803719C7@xxxxxxxxxxxxxxxx
Dear firends,

I have a MS Access 2003 database having 3 files:
1. MDB - Back End file (contains: data)
2. MDE - Front End file (contains: forms, reports, queries, VBA)
3. MDW - Security file (contains: users and groups)

All 3 files are located on a server. There is a shortcut placed on user's
desktop. The shortcut points to MDE file and includes /wrkgrp for the MDW
file. All the users are in same custom group in MDW file having Admin
permissions.

Each user should have a copy of the frontend MDE on their local workstation.
Otherwise you risk corruption in the frontend. I do find it odd that you
would put all the users in a group that has administer permissions in the
database.

When the first user logs in, everything is fine. Then any consecutive
users
logs in, they get message box saying:
"You do not have exlusive access to the database at this time. If you
proceed to make changes, you may not be able to save them later."

That is another reason to give each user their own copy of the frontend.
You'd need to modify their shortcut to point to the location of the frontend
on their computer. They can still use the MDW on the server. Make certain
that all users have the proper Windows permission on the folder where the
backend/mdw are located (modify permission is needed).

This message box appears about 30 or 31 times.

That is due to Adobe version 7. To fix...
Control Panel, Add/remove programs, find Adobe, click Modify -> create Adobe
PDF. Expand to Acrobat PDF Maker and expand to locate Access; deselect the
add-in for Access.


--
Joan Wild
Microsoft Access MVP


.

Relevant Pages

  • Re: Split Database Security Problem
    ... Both frontend and backend ... > permissions, but as in all good stories there is a catch. ... The newAdmin for the 'object database' has the ...
    (comp.databases.ms-access)
  • Re: Split Database Security Problem
    ... Both frontend and backend ... > permissions, but as in all good stories there is a catch. ... The newAdmin for the 'object database' has the ...
    (comp.databases.ms-access)
  • Split Database Security Problem
    ... I have managed to secure a split database. ... Both frontend and backend ... permissions, but as in all good stories there is a catch. ...
    (comp.databases.ms-access)
  • RE: table lock
    ... it is imperative that you split your database ... Once you have the application split, you can save the frontend as an mde ... mde data base to retrieve specific info while on the phone with a customer. ... how can i allow multi users to use the mde file? ...
    (microsoft.public.access.modulesdaovba)
  • Re: Database design for a network
    ... Sooner or later your frontend MDE is going to become corrupted and unusable ... >>> the backend file. ... >>>>in a folder which all users for whom the database is ...
    (microsoft.public.access.gettingstarted)
Loading