How do I password-protect parts of my database?



I have an information database for a small organization (our church,
acutally) and want to allow only certain parts of the database to be
available to certain people. (i.e. all secretaries can see families'
addresses, but only a few people who know the password can see donation
information.) Any ideas?

Rick B

Yes, set up user-level security and then define what they can and can't do.
This will require each user to enter a userid and password ONCE each time
they open the database, then they will only have access to the objects and
functions you define. No need to have annoying password popups everytime
someone tries to access a "secured" area.

Make a backup first, then follow all the instructions IN ORDER.

I'd recommend reading the following a couple of times before you start.
User-Level security is not EASY to implement.

Rick B

Security FAQ

The Security Whitepaper is also worth reading to help you understand.

Joan Wild:

Lynn Trapp



Jeff Conrad

Here is some previous information I have posted in the past:
Access User Level Security will provide the *best* security
for you, but if you just need something simple for a single form
and/or report you could try these Microsoft KB articles:

Implementing Access User Level Security (ULS) *IS* a complicated process
until you get the hang of it. Diligent study of the topic from various sources
and practicing on dummy databases until you "got it down" is really the
best advice. Once you understand ULS it becomes a very valuable tool
in your arsenal. You have more control over the application and what
people can and cannot do.

I would recommend ALL of the following reading material before
jumping into ULS if you want to pursue this topic:

Do not expect to master the subject in an hour, give yourself time.
It can fulfill all your security needs, but many steps need to be
taken before that can happen. Just remember too that ULS has
its own limitations.
Good luck,
Jeff Conrad
Access Junkie

in message:




if you want to do it for real you can do an Access Data Project-- they
have a lot better security.. and you can find a Jr SQL Server developer
anywhere.. Modern copies of Access include a license for MSDE-- this is
a freeware version of SQL Server.. so you would keep it installed on
one machine in the office and that would be the database server.

ADP just has a lot better, easier and more powerful security... it
could be a little bit more difficult to setup; but probably worth it in
the long run.


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question