Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Workgroup Security

Status
Not open for further replies.

iamedwardkim

IS-IT--Management
Nov 7, 2002
29
US
Hi,

I have been attempting to use the Access User and Group Permissions using the Wizard and also by configuring it manually. It all seems to work fine when I am working on my personal computer, but once I try and access the database from another computer on the network (one with a different .mdw file), the database will open without prompting for a username/password and allows full access.

How can I have the database maintain its security from all computers that access it? I know I should eventually have all these computers join the workgroup file that I created but shouldn't it not allow users who aren't part of this workgroup access to the database?

Thank you.
 
Take all the permissions away from the Users group, the Admins group, and the Admin user specifically. That will prevent "double-clickers" from using your DB unauthorized.


The simplest (and least secure) way to prevent this behavior is to have the autoexec macro open a form, and in this form's Open() event, do:
Code:
If CurrentUser like "Admin" Then
    RunCommand acCmdExit
End If

This will close the database without letting the user do anything. --
Find common answers using Google Groups:

 
The Users group as no permissions and I can't seem to delete the "Admin" user. However the "Admin" user has been removed from all groups except the Users group. Still no luck.
 
One more step. In the permissions, where you removed the Users and Admins group from form/table/query permissions, switch over to "User" from "Group". You should see the Admin user, which by default has access to everything, with or without group membership. Uncheck everything. --
Find common answers using Google Groups:

 
Make sure you're implementing security correctly. If you do, this problem goes away.

Here's the short version of how to do it:

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.



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top