MS Access Security

I have a client who is trying to set up the database in Microsoft Access and they want to have two levels of security - an admin who can make changes and a basic user who has read-only access. I haven't found any straight forward documents that tell how to do this. Someone suggested a command line with the/RO option, but that's not really security. Does anybody know how to create a user level security feature?
Sven MogelgaardAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Kent DyerIT Security Analyst SeniorCommented:
Microsoft Access does have a tool..  Called WRKGADM but you do have to run this from a common share or re-apply the file to each workstation.



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Boyd (HiTechCoach) Trimmell, Microsoft Access MVPDesigner and DeveloperCommented:
It is true that Access used to have User Level Security (ULS) in the older JET (.,MDB) database format. It was dropped in the new ACE (.accdb) format. Most people are migrating away from it since it was very difficult to implement correctly

If you are interest in the old ULS technology then see: Jack MacDonald's How I use Microsoft Access User-Level Security

Whatever method you use you will want to split the database.

To keep it simple, make two front end. One for the admins. And One that is read-only.

Read-only can be handled with windows file permissions on the back end or in the front end by setting the forms to not allow edits, deletes, or additions.

Also see this example of a common way to handle user security with a single front end

Boiler Plate Database

This is a moderately advance database that incorporates a number of functions such as 1) user logon 2) table reattachment 3) user tracking 4) how to control access via the use of modal switchboards and more. FYI: Username = admin; Password = admin.
Sven MogelgaardAuthor Commented:
I will check out the tool. But will likely just create two front ends.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Office

From novice to tech pro — start learning today.