>Just for the record, I don't use Triggers to log changes. And as far as viewing the log file - via a VFP report - this feature can be set on/off by the user of the application.

Obviously, different opinions and different approaches out there.

My reason for usually advocating triggers - they are going to fire regardless of what process changed the row. It could be a DBA manually changing some rows, or an overnight ETL process to load data from a legacy system, etc. Many different scenarios where a table could be updated, but the trigger will always fire.