Different security setting for different database

[JeffP]

I want to set up one mdw file for one application on a shared network. I set
it up and now all databases use that mdw file. How do I get around this. I
want to set up two users on a database with less than admin rights. The
databse application is stored on a shared drive where the two users can open
it. How do I do this?

 

[Rick Brandt]

I want to set up one mdw file for one application on a shared network. I set
it up and now all databases use that mdw file. How do I get around this. I
want to set up two users on a database with less than admin rights. The
databse application is stored on a shared drive where the two users can open
it. How do I do this?

Databases don't use mdw files, sessions do. When you created the mdw file
you also made it your default so every Access session you start asks for a
login. Use the Workgroup Administrator utility to change your default mdw
back to System.mdw. Then create a custom shortcut to open your secured
file that specifies the other mdw file as a command line argument.

 

[JeffP]

If i create a shortcut, the user can still open the secure database file
without using the shortcut and has admin rights. What am I missing with the
shortcut. Can it be setup so only the shortcut can open the database. Hope
that makes sense.

 

[Rick Brandt]

If i create a shortcut, the user can still open the secure database file
without using the shortcut and has admin rights. What am I missing with the
shortcut. Can it be setup so only the shortcut can open the database. Hope
that makes sense.

One of my canned responses...

If you can open the file with any mdw file besides the one it was secured
with then you didn't secure it properly. Most likely the default user
"Admin" is still listed as the owner of the database and possibly of all of
the objects. In that case all your security efforts thus far have been
useless.

Get the security FAQ, read it thoroughly several times, and then try again.