A Tricky Security Problem

[Jeffx]

In Access 2003 we use an mdw file (unfortunately named system.mdw) that people are joined to (by using Workgroup Administrator) when they become a new user on the system. This works well except that it is time consuming to go through the process for every new user. I am aware that you can create a new mdw file using the user-level security wizard however I have extra problems. This was set up originally when access 97 was in use and the no of users was about 4, there are now 50 plus and growing. We have numerous databases that are all secured through the use of the same mdw file, however as people are only joining this mdw (by using the Workgroup Administrator), when we get someone with a little computer savvy they will figure out that by creating a generic system.mdw file they can escape all security levels that are in existence in the system.mdw file that we want them to use.
Is it possible to somehow get a database to associate itself with an mdw after the mdw has been extensively modified?
I am aware of short cuts that have the mdw file in them but they are easily bypassed. Furthermore as we have numerous probably 100 databases all pointing at the one mdw file is it possible to get them all associated with the same mdw file? I have looked through the forums and various others but have not found an answer that will help me. Can anyone help?

 

[Dennisk]

Jeffx,
if a database is correctly secured then you cannot bypass the shortcut, as just clicking on the database will produce a security error message.

 

[Jeffx]

Dear Dennis K
I never said it was correctly secured, that is part of my problem. The system.mdw file that I am using does contain all of the users info, however, as it wasn't originally setup using the user level security wizard from within access, and is an original system.mdw that users are joined to then the workaround is possible and the database itself isn't associated or linked to the system.mdw. Currently the users are setup pointing to the system.mdw that has been used all this time and this works to a point, as long as your users aren't inquisitive.

Do you think it is possible if I setup a new security file and call it abcxyz.mdw, and then do the same for every other database we have, then at the end rename the existing system.mdw we are using to abcxyz.mdw. This would have the information in it that we are wanting to use and all the databases would presumably be looking at the same mdw file that we want them too?

 

[gemma-the-husky]

why is it time consuming to add a user to a rights fiel

just put the user in the appropriate groups - about 30secs

 

[Dennisk]

why not take a copy of system.mdw. One for each database and rename it to the name of the database then store it in the same folder as your database. Finally reinstall access to obtain a clean copy of system.mdw. You can then apply the security correctly to each database.

PS. what's is the purpose of putting user names into a workgroup if all your dbs are unsecured?

 

[Len Boorman]

Got a couple of documents (too big to post) on security that may give some help on how to correctly set up security which may offer some help. PM me with an demail address and I will send.

Len