Database Security

[Knowledge]

URGENT! Security bug!!

Last week I installed an Access Database on a server. I split the database into Front End and Back End because there are a couple of persons using this database. After I did that, I created an Office workgroup on the server. I then applied this new workgroup to my new database and added users and passwords with permissions to my database. Everything seemed to work perfectly. The way they are connecting to the database is through a "mapping drive" to the folder that sits on the server.

The problem is that when they open the database, it doesn't ask for any passwords. The only time it asks for a user name and password, is if you open it directly on the server...but that doesn't help me....

I wanted to add a database password, but they need different rights on that database (admin and read-only).

Is there a way I can make this whole security thing work??

Thank you so much for your help!

 

[Ade F]

I may be way off here

Have you gone to the users terminal and added them to the security file using the application

Wrkgadm.exe

located usually in the

C:\Program Files\Microsoft Office\Office\1033

folder (this may vary according to installation just do a search for it.)

Hopefully you used the security wizard and produced the secured.mdw file. With the above application you have to join the secure workgroup by pointing the Wrkgadm.exe @ the Secured.mdw file. Thus when a user opens the database the security file is accessed first.

Hope this helps.

If not and I'm off on a tangent then I appologise.

Regards

Adrian Fiddy

 

[Knowledge]

OOOOOHHHHH!!!

Okay, so let me get this straight : I have to go on the computer of everybody using my new application and create a workgroup on their computer and then link it to my Access application? So if I have 5 persons using my application, I have to go on the computer of these 5 persons and create a workgroup. Is that it? I created one on the server and I thought before opening the database it would check the workgroup ON the server (where the Access file is).... I feel stupid now.....

 

[Ade F]

Not really

You have to go to the users terminal and run the Wrkgadm.exe (assuming the terminal has this program installed if not then this must be installed or copied onto the local drive). It is then a case of running the program and going through your network to the secure.mdw file that was created by the security wizard within access (If you do not have the secure.mdw file then go to Tools\Security\Security Level Wizard when this is set up and the secure.mdw file is produced you will be in business.

As I was saying run the Wrkgadm.exe file and traverse your network to find the secure.mdw file this will then join that terminal to the database security file thus prompting the user for the password you assigned them with the security wizard. Any changes to passwords etc are then done through the other security tools within access.

Of course you must be have DB administrator rights to acheive most of these actions.

Hope this makes sense

Regards

Adrian

 

[Knowledge]

By running this wizard, doesn't it encrypt the database?

 

[Knowledge]

I already have a .mdw file that I created to secure this database (and it works). Could I use this one instead of creating secure.mdw?

 

[Ade F]

I have reached my limit

I'm only going by past experience that the best route is to run the sec wizard on your DB and create the secured.mdw file this will hold all user related rights.

If you have not done this then I suggest you do. Other than that I have reached the limits of my technical scope on this matter.... sorry!

It works for me but I suspect there are real experts out there that can come up with a water tight suggestion.

Any way I'm off for now good luck.

Regards

Adrian

 

[Knowledge]

Thank you so much

You helped me solve my problem! I tested it on the network here and it works perfectly!

I didn't have to run the security wizard because I had already created a workgroup and linked it to my database on the server. I just had to run the wrkgadm.exe on other computers, click "join" in the dialog box and browse to my mdw file. It works perfectly!!


I appreciate your help!

 

[Ade F]

Thanks Pat

So essentially from reading what I have written what incorrect information was I providing Knowledge? I would just like to know for future reference.

I was trying to get across that the secured file resides with the within the DB directory although maybe I made it unclear. And that each terminal does not have to produce this file merely join it.

Regards

Adrian

 

[Ade F]

Thanks Pat

Thank you for your insight.... Much appreciated

 

[Len Boorman]

Excuse me joining but having just gone through the trials of producing a totally secured database I would emphasise a couple of points.

The faq's that Pat referred to. Print off the whole lot and as Pat says read many times.

Print off from http://www.jmhare.com/dbsecurity.htm.

This is a handy document to guide you through the stages BUT it is not complete. You need also to track through this document and the security faq's at the same time. This referenced document is easier to read but consider the faq's the master document and do any extras that this mentions.

Finally I found that the best solution for me was to remove all rights to the default users and groups and use my own users and groups. This way I avoid any possible slips that could allow access from an unauthorised user.

Hope this helps

Len B

 

[hooi]

I'm not able to locate the file 'Wrkgadm.exe' in any of the folders in my PC. I'm using Access 2000 and XP Developer running on W2K Prof. Could someone direct me to the right folder or post the file here please? Thanks...

 

[Autoeng]

For A2K only...

The developer or application administrator can create additional workgroup information files using Wrkgadm.exe. This file can be found at the following location:
C:\Program Files\Microsoft Office\Office\1033

 

[hooi]

I've searched my office and home PCs in the folder location and also searched the entire harddisks for the file. The file simply does not exist in my systems for some reason. Could someone post the file here if the file is not too big please?

Thanks...

 

[Autoeng]

Hooi:

I don't think that will work as executables generally have to be installed and setup in the registry to work. The file is 64K so I can upload but I really think you would be better off reinstalling Access.

 

[hooi]

Thanks Autoeng.

I called local Microsoft customer care and realised that I'm actually using Access 2002, not Access 2000 as I always thought. My apologies.

 

[Autoeng]

Duh...