Table Design... Wondering about security

[maura]

I have a new database that I am designing and I am wondering about some of
the fields that I DO NOT want the end user to have access to... Does Access
have the security to block out an end user from seeing these fields, yet
gives access to an administrator?

Do I need to consider this in the design of the tables, or is this something
I will have to code (once I have gotten to the point of having forms).

Thank you, maura.

 

[Jerry Whittle]

To keep some users out of certain fields, you will need user-level security
and really lock down the tables, queries, forms, and reports.

 

[John Vinson]

I have a new database that I am designing and I am wondering about some of
the fields that I DO NOT want the end user to have access to... Does Access
have the security to block out an end user from seeing these fields, yet
gives access to an administrator?

Do I need to consider this in the design of the tables, or is this something
I will have to code (once I have gotten to the point of having forms).

Thank you, maura.

Access security doesn't directly provide field-level security. What
you would need to do is lock down security *tight*, and not allow
users any access to the tables AT ALL; they would only be allowed to
interact with the data via RWOP (Run With Owner Permission) queries
which let them see only those fields that they should see.

It can be done, but you'll need to really work carefully with the
Access security model.

John W. Vinson[MVP]