Table security

[JO]

In Access 2003, using expanded MDB workgroup information file security, can I
restrict users in a group to full permission with only each user's own data?
Or will this need to be handled programatically?

 

[Rick B]

Unless their data is stored in separate tables, you would need to handle
this through filters or code in your queries, forms, and reports. The first
step would be to take away all access from the tables so they cannot simply
go around your security. You'd then build queries and set them to "run with
owner's permission" so they could use the tables (to which the user would
not otherwise have access).

Use filters like...

=CurrentUser()

to limit the queries to only return the current user records.

 

[Rick Brandt]

In Access 2003, using expanded MDB workgroup information file
security, can I restrict users in a group to full permission with
only each user's own data? Or will this need to be handled
programatically?

You deny all all access to tables directly and use
Run-With-Owners-Permission queries instead. Those queries can have criteria
that uses the CurrentUser() function so that a user can see only his own
records.

 

[JO]

Thank you for your suggestions Rick. I will dig into the "run with owner's
permission" queries working with functions like =CurrentUser() as a solution.