Using an existing Security.mdw to secure new DB

[Guest]

I am using Access 2003.

I am able to use the existing Security.mdw file to access the new DB by
creating a shortcut to the new DB and the existing Security.mdw file.

The problem is that the new DB can still be open without using the shortcut
and therefore has no security !!

Any help would be great. Thanks

Daniel
NRMA insurance

 

[Rick Brandt]

I am using Access 2003.

I am able to use the existing Security.mdw file to access the new DB
by creating a shortcut to the new DB and the existing Security.mdw
file.

The problem is that the new DB can still be open without using the
shortcut and therefore has no security !!

Any help would be great. Thanks

Daniel
NRMA insurance

You have to be logged into the secured workgroup before you create the file
(so "Admin" is not the owner) and then turn off permissions to "Admin" and
"Users" for the database object and all "new objects". Then as you create
or import objects from other files they will automatically have these
minimum security requirements.

 

[Joan Wild]

I am using Access 2003.

I am able to use the existing Security.mdw file to access the new DB by
creating a shortcut to the new DB and the existing Security.mdw file.

The problem is that the new DB can still be open without using the
shortcut
and therefore has no security !!

Permissions are stored in the mdb file. The mdw contains just
usernames/PIDs/passwords/Group membership, etc. Just opening your mdb with
a secure mdw doesn't secure it. Proceed to assign permissions in the new
DB.

 

[Guest]

Rick,

You are a life saver, I can not thank you enough.

THANKS !!