MDW file

[Paul]

I loaded a "homemade" Access DB onto my computer. I had to
use the WRKGADM.EXE utility to join it's MDW file so I
could troubleshoot the problem the user was having with
the DB. I needed full access to it. Now, ALL of my other
Access DBs have this DB's same security. In other words,
all my other DBs that didn't have security, now have
security.

If I use the WRKGADM.EXE, again, and join the MDW file
located in the C:\Program Files\Common Files\System, the
security is back off of my DBs but also the DB I am
troubleshooting. Why is that ?

I would like to be able to have the security for the DB I
am troubleshooting but at the same time, I don't want this
security on my other DBs. Can this be done ?

Thanks,
Paul

 

[Rick Brandt]

I loaded a "homemade" Access DB onto my computer. I had to
use the WRKGADM.EXE utility to join it's MDW file so I
could troubleshoot the problem the user was having with
the DB. I needed full access to it. Now, ALL of my other
Access DBs have this DB's same security. In other words,
all my other DBs that didn't have security, now have
security.

If I use the WRKGADM.EXE, again, and join the MDW file
located in the C:\Program Files\Common Files\System, the
security is back off of my DBs but also the DB I am
troubleshooting. Why is that ?

I would like to be able to have the security for the DB I
am troubleshooting but at the same time, I don't want this
security on my other DBs. Can this be done ?

Access User-Level security is "per session" not "per file".

Keep the unsecured mdw as your default and then create a shortcut that opens the
secured one. That shortcut can include a parameter that specifies the use of a
non-default mdw file.

"Path to MSAccess.exe" "Path to MDB" /wrkgrp "Path to mdw"

 

[Paul]

Gonna give it a try.