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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access Security Wizard

Status
Not open for further replies.

tmcneil

Technical User
Nov 17, 2000
294
US
I posted this question on the General Discussion forum, but I thought I would try here to. I would like to secure my database for two types of users, read only and read/write access. I have used the wizard, but do not feel it is informative enough to do what I need to do. My MS Press book is also not informative enough. I've tried to setup a workgroup info. file, but when I add users to the database, I can never login as those new users to be able to test it. Only myself and the admin have access to the secured database. If the wif file is supposed to store the user names and Passwords, why can't I login as one to test it? Any help the get the security working correctly, would be great.
 
Read the FAQ,s under general by Elisabeth and follow the links it sure helped me understand it
 
On our network which run NT4 on the server and WIN95/98 on the clients we handle database access rights using the permissions property of NT4, assigning read only and read/write access to the various persons/groups as required. May be not so comprehensive as Access security but its a lot easier to achieve the desired effect!
 
It sounds like your user accounts are coming back with the "Not a valid account name or password" box, right? If so, it seems to me you must not be joined to the right Workgroup Information File. After you ran the wizard, did you run the Workgroup Administrator and join the new workgroup? That step is easy to forget, since it runs outside of Access.
 
Thanks for the help, but I figured out the problem. It was kind of stupid. Since I could not get my test-user to login, I needed to check the permission rights to the objects in the database on both front and back-ends. Access hides the database objects permission rights, so obviously i had none of those checked on. I checked those on and it all works. I hate MS sometimes and I would have never found it if someone did not point it out to me. So, if you are using the security, make sure you have the permissions set for the database object and everything will work fine. My co-workers are using what I developed now and I will be making changes in the future.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top