You might be able to pull it off with a filed level validation; if the user does not have write privileges do not allow the update on that field.

>I remember integrating a "custom" module with the ABBRA HR (it's foxpro) package. The ABBRA DBFs had fields that began with a "_". These fields were read only (only internal ABBRA routines could write to them).
>
>Is there a utility or white paper that explains how this is done. Could it be a wish-list item - oh - and while I am at it - how about a password field type that cannot be read outside the application runtime!!!
>
>Thanks