Security Wiz

[WillieLoMain]

I have 2 win2k file servers in my office (no active directory installed). Each is for a different business and each is accessed by different sets of users.

Server A has many Access databases on it While Server B has only one access database at this time.

I want to secure the database on server B but could not run the wizard because it will not run uner termianl services.

So I opened the database from my worksation and setup the secure database that way. Now evey time I access any database from my machine - it looks for the password setup for that single database.

Is this the way this is intended to wrok.

I guess my question is that I am only wanting to have user level security for this one database - is this possible and if so how is it done.

Thanx

 

[FancyPrairie]

Two things to consider.

1. When you setup security, did you create a new workgroup? And does that workgroup reside on the server?

2. You may have modified your copy of the System.mdw file, which is the one Access uses by default. If you did not make a backup copy of it prior to securing your database, copy the System.mdw file from your Access Installation disk. But before you do that, there's a good chance that the Registry on your machine is now pointing to the new workgroup, you created, rather than System.mdw. To check this out, on the task bar, select Start then run. In the Run box, type Regedit. Then selected (via the menu bar) Find. And search for either System.mdw or the name of your new workgroup file. If you find the name of your new workgroup fle, that's your problem. Change the registry entry back to System.mdw. But be carefull. You don't want to damage the registry. You should make of copy of the registry prior to changing it (if you're unfamiliar with changing the registry). To make a copy, goto File | Export.

 

[JeremyNYC]

I would suggest that you get your hands on the ms access security white paper and read it several times (if you get frustrated reading this document, just remember, it's dense, not you). You can get it from ms or from the developers' section of my website.

Also, you can change the workgroup you're joined to from inside access, you don't need to get into the registry. From the tools menu, check which workgroup it is. If it's system.mdw, then, yes, you'll have to recopy it from the cd or from another machine that doesn't exhibit this behavior. But I never touch my registry unless there's no other way to go about it.

What you'll want to do once you get all this sorted is to leave the system.mdw alone and create a new workgroup file (you can use that same menu item on the toolbar) and secure that. Once you do that, you'll rejoin the default workgroup. Then you'll create a batch file or a shortcut that opens your database using the newly created mdw. But all that is written up in the faq/white paper.

Jeremy

==
Jeremy Wallace
AlphaBet City Dataworks

http://www.ABCDataworks.com

Access Databases for Non-Profit Organizations

Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.

 

[FancyPrairie]

Jeremy, I'm not sure this is always correct "you don't need to get into the registry". When I first started messing around with security, I did it incorrectly and Access made my new workgroup the default workgroup. Consequently, Access updated the registry with my workgroup as the default. I didn't what that, I wanted System.mdw to remain my default workgroup. Therefore, I had to go into the Registry to change it back to System.mdw. But you're right, you have to be very careful when you're messing around with the registry.

 

[JeremyNYC]

Yah, now I see your point. I hadn't figured the person's system was in that much trouble yet, but I suppose it's difficult to tell from what's up here at this point. Point well taken.

==
Jeremy Wallace
AlphaBet City Dataworks

http://www.ABCDataworks.com

Access Databases for Non-Profit Organizations

Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.