By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,689 Members | 1,915 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,689 IT Pros & Developers. It's quick & easy.

Database login / security general question

P: 374
I am currently producing a database in access 2003 which will eventually be used with multiple users across my company network. I know about creating a front end / back end and I can understand why however my main issue is security and managing users.

From what I have read you should assign users to groups and create a seperate admin account. I know you can do this within access using the built in wizard (I am yet to attempt this though). However, do I still need to create a seperate user login system? or is this an extra part so basically a form that will popup at the start asking them to login. I would like to be able to add users to the database myself and supply them with a username but I am unsure how this all fits together.

Also when I add a new user to a group within the access security wizard bit would I have to redistribute the front ends out to all users? I'm just trying to get my head around the order you do things and what is required for this security.

Thanks for any help,

Jul 12 '10 #1
Share this Question
Share on Google+
4 Replies

Expert 100+
P: 107
When you use the built-in security wizard and add a password for the admin account, Access will prompt users for a login and password. You do not have to distribute a copy of the front end to all users to use this security feature. You should, however, distribute a link to startup your Access database such that it connects to the security workgroup.

Note, however, that the built-in wizard is not included with later releases of MS Access. It is also not a very secure system since there are programs to extract the passwords that are easy to get.

If your many issue is NOT security, then using the built-in security wizard or creating your own login system is okay. If security is important you might want to consider using SQL Server for storing the data and research how to use SQL Server's security features.
Jul 12 '10 #2

P: 374
Due to the nature of my position within the company and to be honest my lack of knowledge in the area I think im pretty much stuck with using just a split database with back end located on a server without using the sql server option.

DO you know of any good walkthroughs regarding this connecting/distribution of workgroup. I would like each user to have their own front end but as I said I dont get how access can update all of those front ends when I add someone to the group I assume this is where the security workgroup comes from?

Although im thinking creating my own login system might be pretty easy to sort however some insight from those who have done either and have some experience is welcome
Jul 12 '10 #3

Expert 100+
P: 107
Connecting to the workgroup is done through the shortcut. The workgroup has all the security information, so the front-ends do not need to be modified.

The format on the command-line for the shortcut is:
“path and filename for msaccess.exe” “path and filename for mdb” /wrkgrp “path and filename for secure mdw”

A walkthrough for Access security is at:

An additional source of information is at:
Jul 12 '10 #4

Expert 100+
P: 107
I remember there is a quirk with Access security where someone opening the mdb file directly (instead of using the shortcut linking to the security workgroup) gets full permissions, unless the right settings are put in place.

Checking , step 11, it seems the trick is to remove all rights to the Users group.

I recommend checking out that site and going through the security tutorial.

Step 11 states:
In the next wizard dialog box, accept the default selection "No, The Users Group Should Not Have Any Permissions". Any permissions you assign to the Users group are the same permissions available to anyone with a copy of Access. You want to completely lock out others.

You'll also want to be sure you have at least one account for the developer that is in the Admins group.

I think there is an extra gotcha associated with the Admin account where it needs to be locked down. Does anyone have info on how to handle the Admin account when securing an mdb using the built-in security?
Jul 13 '10 #5

Post your reply

Sign in to post your reply or Sign up for a free account.