Open Database from shortcut only 2

[chadrj]

I would like to set up my database for use on a shared drive so that it may ONLY be opened through use of a shortcut. I am afraid that users will access it directly and have admin rights per their default mdw file, but I don't want to change their default mdw file as they need to access other databases fully.

 

[GDGarth]

If you set up security properly, users won't have full administration rights under the default system.mdw.

you can set it up so the default admin user has no rights and can't even open up the database.

Be sure to follow the security instructions exactly, or your database won't be really secure.

 

[chadrj]

Perhaps I am not setting up security properly, but when I change permissions in Access doesn't that just change what permissions one has if they are using same mdw file? Is there some other way to restrict the Admin user within the database so that if anyone logs on using the default system.mdw they can't open the database?

After reading JeremyNYC's post the following is to inform you of what I have done to this point:

I created a new workgroup file (Jdd.mdw) and placed in on the shared drive so everyone can use it when I get this right. With the advice of GDGarth, I took all security away from the Admin user and created a new Admin user (DBAdmin). After doing this, things work pretty well if I use my PC, though Admin can still open the database, just can't view any data or forms or anything. If I go to someone else's PC, they can open the database and have free access to everything in the database (obviously they are using their own system.mdw) I have searched Access Help, I have the scoured Microsoft Access 97 Developers Handbook, and Mastering Access 97 for Windows 95/NT to no avail.

Any and all help is appreciated!

 

[GDGarth]

Here's the abbreviated version of the steps (I'll try not to leave anything out, but if I do, somenone will correct me, I'm sure):


Run WRKGADM.EXE and create a new workgroup, using a new name and ID (DON'T just copy System.mdw).

Make sure you are joined to the new workgroup.

Open the database while joined to the new workgroup.

Create a new user name, and make sure it is a member of the "Admins" group.

Remove the "Admin" user from the "Admins" group (leave them a part of the "Users" group).

Run the User-Level Security Wizard to make a secured copy of your database. Move your original, unsecured database to a secure location, in case you need it (unlikely).

At this time, only members of the "Admins" group have permissions in the database. Open the secured database under your username, create users and groups as required, and assign permissions.

I just ran through this procedure with someone here at work, and we then verified that the default user couldn't do anything they hadn't been allowed to do through security.

 

[chadrj]

Thanks for your help! It works fine now. I just needed to run the wizard, I guess that links the DB to the security or something like that.

 

[JimInKS]

chadrj,
Glad it's working for you.

I think your original problem was that you had created all the appropriate user accounts but you had not set the User and Group Permissions on the database you were trying to secure.

In particular you would have to take away all rights from the Users group. Then add the rights for the new users and groups you had created. I'm sure the wizard did this for you.

You view/set permissions in
Tools, Security, User and Group Permissions...
-or-
Use the Security Manager Add-in. Much easier to work with.