For a VFP DBC this is correct. You can not replace data in an UPDATE trigger because this is also considered an UPDATE that fires the UPDATE trigger. So you could be caught in an endless loop. However, this is not the case for SQL databases. An update trigger can update values of columns in the table being updated because the SQL used to update the table is intercepted by the update trigger where you can set the "NEW" values of the columns to whatever you want before the data is posted to the table.

What you should use for a DBC is the Record Validation rule in the table.

>Hi
>
>Is it right that you can't issue a REPLACE for the "updating" table in an UPDATE TRIGGER?
>
>If it is right, then that isn't right, or it's not right, why the restriction?
>
>Thanks
>Kev