Why not allow them to edit this data in a grid where you can better control what they have access to? You could also create a new table of meta data that can be used to determine which fields in each table are editiable. Then use that information to determine which fields/columns in this grid are read only.

>I used to allow customers, when they logged single user, to change data in a simplistic BROWSE, where they could do some emergency changes.
>I used to have just REGULAR indexes.
>In forms I catch uniqueness violations with a VALID.
>
>When I change an index to CANDIDATE now I don´t seem to be able to catch the global BROWSE error when uniqueness is violated by a key field being changed.
>
>Do I need to generate a BROWSE FIELDS with a VALID clause for the unique field for every table in question now?
>Thanks
>G