Even if you added security, a persistent intruder could probably bypass it.
If your users are ONLY using forms to access the data, link to the other
table/database, create a query that ONLY returns the fields you wish them to
see, and use a form to display that info.
(if your users look at the tables, or write their own queries/SQL in
procedures, they'd still be able to see other fields).
A more drastic, and labor-intensive (your labor) approach would be to use
code to open a link to the other db/table, update a "local" table with ONLY
the fields permitted, then break the link.
How hard do you want to work at this, and how secure is "secure"?

Signature
Good luck
Jeff Boyce
<Access MVP>
> Hello,
>
[quoted text clipped - 7 lines]
> Thanks,
> Linda
LMB - 15 May 2005 22:30 GMT
I wouldn't have time to update the table each time a change was made but
perhaps the secretary could do that manually on a weekly basis.
Thanks,
Linda
> Even if you added security, a persistent intruder could probably bypass
> it.
[quoted text clipped - 27 lines]
>> Thanks,
>> Linda