Is there another way to secure a database using a different MDW file?

[JLandis]

Hello, I am trying to secure a database with a unique
system.mdw file. I have read about creating a shortcut
and it works - however, I really don't want to have to
touch all of my users' PCs. Is there another way to
associate a specific database with a unique system.mdw
file? Any suggestions would be GREATLY APPRECIATED!!!
I'm running out of options!

 

[Rick Brandt]

Hello, I am trying to secure a database with a unique
system.mdw file. I have read about creating a shortcut
and it works - however, I really don't want to have to
touch all of my users' PCs. Is there another way to
associate a specific database with a unique system.mdw
file? Any suggestions would be GREATLY APPRECIATED!!!
I'm running out of options!

Nope. The mdw file is not "attached" to any particular mdb nor is the MDB
"attached" to any particular mdw file. The mdw file is used first and
establishes who you are and what groups you belong to. Then when the mdb
is opened those credentials are checked against the permissions in the mdb
to see if the current user has proper authority to open the file.

This means there is a relationship of sorts between the two, but not as
hard-coded as you seem to think. A particular mdb might be able to be
opened using only one particular mdw, but that is only because it is the
only one that contains the appropriate users and/or group identifiers, not
from any sort of "linkage".