Protecting some data from some users

[S.M.]

I've got an existing customer database on which I need to add some private
fields to my form which are only accessable to some users while still
allowing all users permissions to edit every other field.

I've only got limited experience with Access, so I'm not clear on the best
way to do this while still maintaining my existing database. Does anyone have
a suggestion?

 

[John W. Vinson]

I've got an existing customer database on which I need to add some private
fields to my form which are only accessable to some users while still
allowing all users permissions to edit every other field.

I've only got limited experience with Access, so I'm not clear on the best
way to do this while still maintaining my existing database. Does anyone have
a suggestion?

What version of Access? With 2003 and before you can use Workgroups Security
(though it's a fairly complex and finicky feature); but this security option
was removed in 2007.

For versions that support it download the Microsoft Access 2000 Security FAQ:

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

Print it out. Read it carefully. Get a good night's sleep; read it carefully
AGAIN. Follow the instructions to the letter - it's easy to get security
wrong!

 

[S.M.]

I'm using 2007 version. Thanks for the response, I'm sure all that reading
would help. I did, however, figured out a solution after a little exploring
and scalp-scratching.

I set the input masks on those table columns to Password and have all the
secure fields on another form which is only accessable by certain users set
through the database users and permissions. I also set it so only the
administrator was able to modify design. This allows me to keep all this info
in the same table and keep the database simple, while still protecting the
info I required.

As far as I know this resolves my problem. If anyone sees a problem with
this design, please let me know.

S.M.

 

[John W. Vinson]

I'm using 2007 version. Thanks for the response, I'm sure all that reading
would help. I did, however, figured out a solution after a little exploring
and scalp-scratching.

I set the input masks on those table columns to Password and have all the
secure fields on another form which is only accessable by certain users set
through the database users and permissions. I also set it so only the
administrator was able to modify design. This allows me to keep all this info
in the same table and keep the database simple, while still protecting the
info I required.

As far as I know this resolves my problem. If anyone sees a problem with
this design, please let me know.

"Locks are to keep out honest people". If you're just trying to keep employees
from seeing and messing around, this should be fine. If you're trying to keep
an experienced Access developer or hacker, someone who knows that the
information is prohibited for them but is determined to get it, you're in
trouble; your security tricks can easily be bypassed.

If you really need data security, Access/JET databases simply aren't up to it
(that's surely why they gave up and removed Workgroup security); you'll need
to use SQL/Server to store the data. Fortunately that's now cheaper and easier
than it was even a couple of years ago.