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

Help me simplify workgroup security for Login IDs 2

Status
Not open for further replies.

JonWolgamuth

Technical User
Apr 19, 2001
53
US
I'm trying to set up a workgroup for my department's users, so they have to login to the application at the beginning. I'm not so concerned with security, so I won't require any passwords of my users, but I just want them to be identified so I can use the CurrentUser () function to help identify the work they do. (It defaults to 'admin' unless the users are forced to login as themselves.

Can anyone help me get this done. I've tried to set up a workgroup and secure the database, but no matter what I do, when I have someone else log in, it bypasses the security, and logs them in as Admin. What am I doing wrong??

I'm beginning to feel a bit defeated...

Jon
 
I haven't done it before, but I know there are a couple of FAQ's that have been written by people that have done it. Did you read them? Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.
 
I've read the FAQs, I've read Microsoft's "FAQs about MS Access Security for MS Access versions 2.0 through 2000" and still can't seem to get it to work to my ends.
 
After I have users "join" the workgroup I've set up for my database, it asks them to login when they open Access. However, when they try to open an unsecured database, it still uses my workgroup, and logs them in. As far as I can tell, it gives them the same rights as I've set up in my database. I don't want that...

I'm getting a headache...
 
Access bypasses the login dialog if the Admin user's password is blank. You have to join your special workgroup, enter Access (as Admin), and change the password to non-blank to make the login dialog display. Note that if you do this, users may no longer be able to open unsecured databases while joined to your workgroup; they may have to rejoin the default workgroup first.

You might be interested in an alternative. It's possible to create a shortcut to msaccess.exe, and modify its command line to specify a user id and/or workgroup information file. If you do this, your users won't even have to use the Workgroup Administrator to join your special workgroup before opening your database, nor to rejoin the default system workgroup before using other databases, because the specified workgroup information file is only effective for the instance of Access being started. For more information, check the Help file index for "command-line options", then select the "Startup command-line options" topic. Rick Sprague
 
Thanks Rick. Now, a couple more questions. If I set up this command line, does this become a shortcut on each user's desktop? Won't the user then be able to open the database directly (without using the shortcut with the command line), and log in as Admin? Can I resolve this by revoking rights to the default Admin login? Okay, that was three questions.

Thanks again for your help!
 
Three questions, three answers: Yes, Yes, and Yes. But better than revoking rights to Admin (unless you want to do that anyway) is giving Admin a password. That way, if they try to open the database directly, without the shortcut, they'll get a login box. (Unfortunately, they'll be in the wrong workgroup file, too, so they won't be able to log on, but at least they won't get the database open and think they've entered it properly.)

Glad to be of service! Rick Sprague
 
This may not help and may not be the thing to do, but here is what I do.

I take away all rights from the admin account, remove it from the admin group, and make an account for myself with full admin rights. This way they will have to enter a valid user name and password to log in. Even if you do just make the password: password.

This is what I am doing in my own DB, and I am using Elizabeth's FAQ under General Discussion to keep a record of who accessed a record, what time and date, and what record. Please let me know if this helps you at all. Thank you for your help and time. It is greatly appreciated!!!

Thanks,
Don
mailto:f613493c@mailfxhome.fedex.com
mailto:mrfilez@midsouth.rr.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top