Security with Database on a Server

[Full_Williams]

Hi there,

I have a security question and any help would be greatly appreciated for I think I might be missing something major here and it's killing me.

I've set up a workgroup information file that's on the server, the database is on the server as well. On one users computer I've created a shortcut passing through the workgroup information file. Everything's working great now. I'm prompted with a password and the user is limited on what she can do once in the database. The administrator has full access. So I go to another computer and bango, I'm able to pull up the database right off the server no problem without having to fill in passwork information. It seems I've opened the database with a different workgroup file since the group I created is not in there.

My question is: How can you attach this workgroup information file to the database so you don't have to create a path that passes through the workgroup? Is this even possible? Since they're separated anybody can open this database up that has access to this network drive. I've been thinking this might just be a downfall of the Access security, but not sure.

Again any help on this would be appreciated.

Thanks,
Full_Williams

 

[ghudson]

If the database is properly secured using Access security with workgroups and user permissions, nobody is going to be able to open, link, import from your secured db without loging in.

All user computers must be joined to the System.mdw file. Never join a computer to the security workgroup file. The System.mdw file is located in the Widows "System" folder.

Your secured shortcut should look something like this...

"C:\Program Files\Microsoft Office\Office\msaccess.exe" /wrkgrp "C:\Databases\DB1.mdw" "C:\Databases\DB1.mdb" /user Group1

Check this site for an article about Access security...
http://www.jmhare.com/dbsecurity.htm

HTH

 

[Full_Williams]

Thanks ghudson,

I have the path down correctly and thanks for the advice on not joining the users computer to the workgroup file. What about the non-users that have access to the network drive that holds the database? They aren't set up in the System.mdw file, but are still able to access the database. Is there a way around this without setting up a "Database Password"? Do you think I just have the security set up incorrectly?

Thanks again for you help.
Full_Williams

 

[ghudson]

It sounds like the database is not correctly secured. If other users can open the db by just double clicking the mdb from Windows Explorer, then you should be able to do the same thing.

Check out that security article I mentioned above. My security ways are so set that I myself would have a hard time remembering how to do it from scratch.

Dooh, I just noticed somethig in your post...Is your security file named "System.mdw"??? I hope not but that would explain your problem. All user computers have the security admin file and that default System.mdw file give all users admin rights to all db's. You never want to touch a computers System.mdw file.

Your custom security file must be renamed. You can either use a new and different security file for each db or use one for all applications.

If the above is true, you need to get your System.mdw file restored (including your users). Maybe copying one from a pc that has never used Access security before should work.

HTH

 

[Full_Williams]

Oh boy, my security file is named "System.mdw" and is on the network. Does it matter that I saved it to the network? Since I created and save the new "System.mdw" on the server am I ok as far as corrupting the users ""System.mdw"? I have a feeling I really screwed things up here. If not, can I just create a new security file, save on the network and name "Secure.mdw" and set up users permissions?

 

[ghudson]

Not as bad as you might think. Since you created a new System.mdw on the server, your computers System.mdw should be okay. I suggest that you rename the System.mdw file on the server and fix the mdw name in your security shortcut there as well. You should then be okay.

HTH

 

[Full_Williams]

ghudson,

I'm going down to the site where the db is early next week so I'll rename the System.mdw file then and see how it goes. Thanks again for your help.

 

[kstuart]

Access Security

Hi Folks,

I have been following this thread as I have the identical problem with a new database I created recently. (My first)

Am I safe in assuming that since the system.mdw file and the database reside in the same folder on my server, renaming the .mdw file will block other access users who are not enrolled in my DB security?

 

[ghudson]

I believe we have left out a few steps.

The reason everybody can access your secured db is because you have allowed the Admin group full access to all objects.

You need to remove the Admin permissions from the database. From the menu bar, click Tools / Security / User and Groups Permissions...

For all objects (forms, tables, etc.), you must select the User/Group Name and DELSELECT the permissions for ALL objects and object names!

I am guessing that you already have created another User Group for your users to log into the db with?!?! If not, do it now.

Your last step should be to assign the permissions for ALL objects and object names that you WANT your user group to view or have access too.

If you (anybody ready this thread) are not sure about any of these steps (or the Access security process), I highly recommend that you read the security article I mentioned above! My ways are so set that I do not have to think about all the little steps so I might be missing something here.

HTH

 

[Full_Williams]

ghudson,

Thanks for your help. I followed that security article to a T and it worked perfectly. For some reason I thought you could secure the database without using the Wizard and I believe that's where my problem was. Anyway, thanks a ton.

Take it easy,
Full Williams