A
Allen Browne
Access does not have true field-level permissions, but I was recently asked
to set up a database where some fields would be locked and others not. The
idea was to allow the user who created the record to make changes, or permit
changes only while the record was new (say for one hour), on a
field-by-field basis, and let the manager change the permissions at runtime.
A custom property on the field, made this simple to implement and
maintance-free. Details and downloadable example in:
Field-level Permissions in Microsoft Access
at:
http://allenbrowne.com/ser-55.html
While it is not true security, it is an adequate padlock for many
applications, and will certainly help avoid unintentional alterations.
This question is not asked often, but hopefully the sample will help some
poster searching for a way to do this.
to set up a database where some fields would be locked and others not. The
idea was to allow the user who created the record to make changes, or permit
changes only while the record was new (say for one hour), on a
field-by-field basis, and let the manager change the permissions at runtime.
A custom property on the field, made this simple to implement and
maintance-free. Details and downloadable example in:
Field-level Permissions in Microsoft Access
at:
http://allenbrowne.com/ser-55.html
While it is not true security, it is an adequate padlock for many
applications, and will certainly help avoid unintentional alterations.
This question is not asked often, but hopefully the sample will help some
poster searching for a way to do this.