security

[Jason]

I currently have my secured.mdw file on a network so that
I can share the security settings. The problem is that if
I lose connection to the server on which the .mdw file
resides, Access will change the workgroup link to a
default. This gives users access to everything in the
application. Right now I am using a shortcut to the .mdb
file that defines the /wrkgrp link, but this is not good
security because users could potentially open the
original .mdb file. Has anyone found a way to fix this?

 

[Rick Brandt]

I currently have my secured.mdw file on a network so that
I can share the security settings. The problem is that if
I lose connection to the server on which the .mdw file
resides, Access will change the workgroup link to a
default. This gives users access to everything in the
application. Right now I am using a shortcut to the .mdb
file that defines the /wrkgrp link, but this is not good
security because users could potentially open the
original .mdb file. Has anyone found a way to fix this?

Once again with feeling

If users can open your MDB without using the MDW that was used to create it then
security is NOT applied properly.

When using the default MDW file to open a file the user is doing so as user = "Admin"
who is a member of the group "Users". In a properly secured file these attributes
should not be enough to get in. At a minimum your security should have the following
as true.

The user "Admin" has zero permissions to the db and all objects.
The group "Users" has zero permissions to the db and all objects.
The user "Admin" is not listed as the owner of the db or any of the objects.

You have missed one of these (usually the last one).