2002 User Level Security

[cjelec]

Hi,

After following Microsoft's tutorial on creating User Level Security, I tried to open the newly secured database and found that I didn't have permission to open it.

The wizard automatically created a user with my name and I added this user to the Admins group. I also created other users and added them to the relevant groups.

I have printed off the Report generated by the wizard, but it doesn't seem to be of any use as I can't open the database.

All I want to do is create a user account system to a single database where there are three users 'Admin', 'Manager', and 'Input'.

Could someone help me with this?

Thanks

[small]And, yes I do have a copy of the database that isn't secure, and I can open it.[/small]

 

[KornGeek]

First, let me applaud you for doing so well so far. You backed up your nonsecured database, and you followed the documentation. Failing to do these two things leads to the vast majority of problems with user-level security implementations, so I'm impressed.

You should also have backed up your mdw file and created a new one for this database. You might want to double check these. Access uses a default mdw file for all databases opened on your local computer unless specifically told to use a different mdw. Also, users on different computers will still use their default mdw files unless told to do otherwise.

What user account are you using to try to open the database? If it's not prompting you for an account, then it is defaulting to the admin account. Setting a password on this account will cause Access to prompt you to login.

My best guess based on the information provided is that the wizard disabled permissions on the database for the admin user and the users group (good idea). You now need to login as a different user to begin using the database.

 

[cjelec]

Hi,

Thanks for your reply.

I am trying to create user accounts for this database only (not every one I create).

The database will be used on another machine, so I don't want it to use the global sec file.

I have found that using the "User and group Accounts" and the "User and group Permissions" windows work, but are they changing the global sec file?

Thanks again.

 

[KornGeek]

Essentially, changing "User and group Accounts" changes the mdw file (most likely the one on your machine only). Changing the "User and group Permissions" changes the mdb file.

It's been a long time since I used the wizard, but I believe that it should have made (or at least offered to make) a new mdw file for you. You would then have to launch your database using a shortcut that invokes Access with this mdw file.

In a nutshell, you want to:
1) Back up everything. Writing it to a CD or some other external medium is not a bad idea either.
2) Create a new mdw file (we'll call it mdw2 as opposed to the original mdw1).
3) In mdw2, create a new group (let's call it users2), and a new login (let's call it admin2).
4) Remove the admin user from the admins group. Add admin2 to the users2 group. Add a password to the origninal admin user.

Note: These are all mdw-level changes so far.

5) Open your database using mdw2. Remove all permissions (including open database) from the admin user and the users group.
6) Assign permissions to the users2 group and/or the admin2 user.
7) Make sure that the admin2 user (and NOT the admin user) is the owner of every component of your database.

8) Once you have done these steps, test. It is likely that you and/or I have forgotten a vital step. Test from your machine. Try to get into the database without linking to the new mdw. Try to get in using the admin user. Try to get in using the admin2 user. Test it every way you can think of. Go to a different computer and try again. Next, go to an end user's computer and try yet again.

 

[cjelec]

Hi,

Thanks again,

Its still is not working, and it is starting to really get on my...

I think that I will create the security on the computer that it is going to be run from, and tell the user not to move it.

The only issue I can see with this, is that if the computer needs to rebuilt no one can have access to the database, or do I backup the main/local mdw just in case this happens?

Thanks