Re: With and Without (not Pink Floyd)

"Dave" <Dave@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:74067082-2BB0-4D18-9048-727286E419B0@xxxxxxxxxxxxxxxx
> Hello,
>
> I have an Access 2000 database running on WinXP that uses two shortcuts to
> open the database. One shortcut is for the administrator that uses the MDW
> file and prompts for the useid and password. The other shortcut is for
> "regular" users that opens the MDB file without security. I want to split
> the
> MDB into a FE/BE configuration and keep the same "simple" security setup.
> I
> can lockdown the BE using a trick found in this discussion group. But,
> when I
> try to use the "regular" shortcut to open the database, I get an Access
> warning msgbox telling me I don't have permissions to the linked tables
> thru
> the FE. Is there a way to keep the Admin/Regular shortcuts?
>

"And after all it's what the fighting's all about."

First off, all Access databases use an mdw file, by default this is
"system.mdw" located somewhere where you installed Office. By default,
"system.mdw" allows full permissions to all users for new databases and
existing ones that haven't been secured. You should not modify "system.mdw"
because it can prevent "ordinary" users from opening unsecured apps.

So your "regular" users are being authenticated against "system.mdw" and
allowed full access? Seems unlikely. Anyway, you need your front and back
ends to be affiliated with the same mdw file. Once you've secured one of
them, stay joined to your workgroup, close the mdb but keep the Access shell
open. Create a new blank database and import all of the objects from the
unsecured mdb into it. Re-link your tables as appropriate.

If you haven't read the MS FAQ on Access security then I recommend you do so
as it is essential reading. There's a link to it on my web site and there's
also a step-by-step example on there too which you might find useful.

HTH - Keith.
www.keithwilby.com


.

Relevant Pages

  • Re: security wizard cannot be run
    ... You need to open your database using your secured mdw (i.e. the desktop ... Open Access (not via the shortcut). ... Create a new mdb and import everything from your 'secure' mdb. ... Once the database opens, the ...
    (microsoft.public.access.security)
  • Re: security not requesting log in
    ... If you had done this, then no matter what mdw file she used, ... Another step you should have performed is to secure the database file. ... and delete all the security files and create a new file. ... opens immediately to the main screen and shows her as Admin. ...
    (microsoft.public.access.security)
  • Re: security not requesting log in
    ... If you had done this, then no matter what mdw file she used, ... Another step you should have performed is to secure the database file. ... and delete all the security files and create a new file. ... opens immediately to the main screen and shows her as Admin. ...
    (microsoft.public.access.security)
  • Creating a shortcut that opens a multi-level security in a runtime
    ... I created a database with one front-end mdb file linked to a back end mdb ... The database is to be used by multiple users so I ... added login and password using Access security facility (using a MDW file). ... I therefore use a shortcut that linke the MASACCESS.exe ...
    (microsoft.public.access.modulesdaovba)
  • Re: Different security setting for different database
    ... If i create a shortcut, the user can still open the secure database file ... Can it be setup so only the shortcut can open the database. ... >> I want to set up one mdw file for one application on a shared network. ... >> want to set up two users on a database with less than admin rights. ...
    (microsoft.public.access.security)