prevent opening MDB without use of MDW

[DUNDAPANJ]

I have made a MYDB.MDB file. I also have made a
MYSECURITY.MDW with the appropriate security for that MDB.
I have created a shortcut like: "C:\Program
Files\Microsoft Office\Office\MSACCESS.EXE" "C:\MYDB.MDB"
\WRKGRP "C:\MYSECURITY.MDW"

It works perfectly if the user uses the shortcut, BUT if
a "smart" user accesses directly the DB (MDB file without
using the shortcut), he will bypass the MDW and thus the
security.

How can I prevent that the MDB can be opened without using
the right MDW file (MYSECURITY.MDW in my case).

I am looking for a method where the database(MDB) can only
be opened if the MDW is used, if such a method exists.

Thank You,
DUNDAPANJ

 

[Jack MacDonald]

If they can open the file without using the designated workgroup file,
then you have missed one of the security steps. I have written a paper
about security that you may find useful. Find a link to it and other
resources on the website in my signature.

I have made a MYDB.MDB file. I also have made a
MYSECURITY.MDW with the appropriate security for that MDB.
I have created a shortcut like: "C:\Program
Files\Microsoft Office\Office\MSACCESS.EXE" "C:\MYDB.MDB"
\WRKGRP "C:\MYSECURITY.MDW"

It works perfectly if the user uses the shortcut, BUT if
a "smart" user accesses directly the DB (MDB file without
using the shortcut), he will bypass the MDW and thus the
security.

How can I prevent that the MDB can be opened without using
the right MDW file (MYSECURITY.MDW in my case).

I am looking for a method where the database(MDB) can only
be opened if the MDW is used, if such a method exists.

Thank You,
DUNDAPANJ

**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

 

[Guest]

Open MYDB as the administrator, using the Admin account user name and password. Add a new user account and password, place this user in the Admins group. Close MYDB. Reopen MYDB as the new administrative user. Remove all permissions from the Admin user account. Remove the Admin user account from the Admins group. Now the 'anonmous Admin' user has no rights within the mdb.

If you haven't already done so, create groups which have the permissions that you need, create user accounts and passwords for all your users, then assign the users to the appropriate group or groups. Make certain that only the user or users that NEED administrative rights are in the Admins group.
HTH
Glen McWilliams