Field Privacy

[autlew]

I have a database that I need the SSN number for employees as the key. I
want to make it so I can input the SSN number when I add an employee but make
it so others that need to veiw the database can not see the number.
How can I do this?
Thanks

 

[Jerry Whittle]

It's going to be pretty much work if the SSN must be hidden from all other
users.

Also you won't be able to use it as the primary key field. Note: using a SSN
as the PK is a bad idea anyway. What happens if you have an employee who is
not a US citizen and therefore doesn't have a SSN?

1. You'll need to implement user-level security. Note that Access 2007 accdb
files do not support user-level security.

2. You'll need to create another table with the the PK from the employee
table as the FK and the SSN field.

3. You'll need to create a one-to-one relationship with referential
integrity enabled.

4. You'll need to restrict who can see the data in the SSN table using
user-level security.

OR

You can just hide the employee table and hope that none of your users are
bright enough to figure it out. That could get ugly fast for you if there was
ever an identity theft incident.

 

[John W. Vinson]

I have a database that I need the SSN number for employees as the key. I
want to make it so I can input the SSN number when I add an employee but make
it so others that need to veiw the database can not see the number.
How can I do this?
Thanks

What I'd suggest is that you create a surrogate key - it could be an
Autonumber - in the employee table, and make IT the primary key; use it for
linking to the other tables.

Leave the SSN field in the Employee table, with a unique Index, but not make
it the primary key; and of course don't include it in any other tables.

You'll need to prohibit access to table design view, and provide forms which
conceal the SSN field from everyone except you (or those authorized to enter
data), using Access security. See the Microsoft Access 2000 Security FAQ:

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

Another MVP very aptly described this document as "thirty pages, no filler" -
it's dense, complicated, and can easily be done wrong, so study it CAREFULLY
and follow its instructions to the letter!