mdw file confusion

[astern]

I have a database that I've secured with passwords and
permissions. I'm also trying to package the database for
distribution (I'm including my mdw file). When I run the
executable on another machine, it sees the default mdw
file, not mine. What can I do to make the database see
the right mdw file???

 

[Rick Brandt]

I have a database that I've secured with passwords and
permissions. I'm also trying to package the database for
distribution (I'm including my mdw file). When I run the
executable on another machine, it sees the default mdw
file, not mine. What can I do to make the database see
the right mdw file???

Unless you instruct all users to change their default MDW file to yours (not
recommended) you have to include it as a command line argument in a custom
shortcut. The syntax is roughly...

"Path to MSAccess.exe" /WrkGrp "Pathe to MDW" "Path to MDB"

PS. Hopefully when these users attempted to open your file with their
default MDW they were denied access (right?).

 

[astern]

No, they were able to open it. Their default mdw file is
just that - the default. (

I will try adding in the shortcut, but that kind of
defeats the purpose of passwording the database. If they
just open the database and not use the shortcut, they are
allowed in.

Any other suggestions?!?

 

[Joan Wild]

You have missed a step in securing the mdb, if they are able to even open it
using the default.

Did you follow all the steps in the security FAQ?
http://support.microsoft.com/?id=207793

Skipping one step would be enough.

Perhaps the Users Group still has permission to something, or the Admin user
owns something.