Limiting access to DB and what forms someone can use

[pctech86]

We have an access database I have created here at work that lets us track
specific information. My receptionist needs to be able to add certain data
to the database, but only needs to have access to a few fields. I have
solved that (i think) by making a form that lets her update certain fields
and that is it. However how do I keep her from using other forms, or going
directly into the database and changing something?

 

[Squik27]

We have an access database I have created here at work that lets us track
specific information. My receptionist needs to be able to add certain data
to the database, but only needs to have access to a few fields. I have
solved that (i think) by making a form that lets her update certain fields
and that is it. However how do I keep her from using other forms, or going
directly into the database and changing something?

I'm not really sure, but you could do a little research on users and
permission for forms. Go to tools-->security and see if you can find
something there that will help you. Also if you want to lack design you can
create a MDE file, Check this website that will tell you about it.
http://www.members.shaw.ca/AlbertKallal/Articles/split/

Hope I helped.

 

[pctech86]

How do I enable ULS?

Method 1:

Give her her own front end db with the objects she needs, linking tables on a
hidden share on the network, and not telling her where the back end is.

Don't give her Windows permissions to use the current front end (no read,
write or modify permissions on the folder where other users get the updated
front end).

Drawbacks: If she knows to look in the msysobjects table, she'll find the
path to the back end tables. Maintaining 2 db front ends is a pain.

Method 2:

Apply Access user level security on the current front end and back end. Only
give her permissions to open/run the forms she needs.

Drawbacks: Access user level security is an advanced topic and hard to get
right the first dozen or so tries. If the user knows where to look for the
tools, user level security is circumventable.

As you can see, both methods have drawbacks.

Chris

 

[John W. Vinson]

We have an access database I have created here at work that lets us track
specific information. My receptionist needs to be able to add certain data
to the database, but only needs to have access to a few fields. I have
solved that (i think) by making a form that lets her update certain fields
and that is it. However how do I keep her from using other forms, or going
directly into the database and changing something?

It depends on how determined she is, how skilled with Access, and what version
you have, to some extent. If you're using the .mdb format (rather than the
newer A2007 .accdb) you can implement Workgroup Security; to do so download
the Microsoft Access 2000 Security FAQ:

http://support.microsoft.com/kb/207793/en-us

Study it CAREFULLY. Get a good night's sleep. Read it again, cover to cover,
even MORE carefully! It's easy to do security wrong.

If you want something simpler, or you're using the new format, or you're just
trying to keep your receptionist from *unintentionally* going where she
shouldn't (as opposed to purposeful snooping), use the database's Startup
properties to open it to the form or switchboard that you want her to see, and
to conceal the database window. The details of how to do so differ by version.