protecting access objects

[Elaine Taylor]

Short of 'hiding' tables, queries & reports in the
database window, is there a way of password protecting or
securing individual tables/reports etc without password
protecting the entire database so that users can't see
actual data once it has been stored?

I don't want a pasword to actually open database as the
general public need to be able open it to enter their data.

I can only think of linking tables in a separate database
that only contains a form & hiding the linked table..

 

[Peter De Baets]

Short of 'hiding' tables, queries & reports in the
database window, is there a way of password protecting or
securing individual tables/reports etc without password
protecting the entire database so that users can't see
actual data once it has been stored?

I don't want a pasword to actually open database as the
general public need to be able open it to enter their data.

I can only think of linking tables in a separate database
that only contains a form & hiding the linked table..

Hiding the tables is one approach that comes to mind. You can also separate
your data into an external database, then encrypt that database, link the
tables from your front-end database, and hide those links once created. Just
some ideas.

For individual report security, perhaps a tool like our LASsie product might
help http://www.peterssoftware.com/las.htm. Or you could use the same basic
concept of keeping a table of users and security levels and just use the
network login ID as the user name (no Access sign-on required).

Hope this helps,