Hi, Victor,

Let's say the database field is amountpaid. I look at a record today and it says $1,000. I look at the same record tomorrow and it says $1,500. Since you hinted that you don't have a reason code, all other columns in the row are the same.

My question is...just by looking at the data and not actually 'seeing' a user change the amount, how would one know why it was changed in the first place?

(Point I'm getting at is that if the reason for the change is that important, it's important enough to store).

I'm not an expert on SQL Server, but I'm not aware of parameters that can be passed to a trigger. You set one up on an update, insert, delete, etc.

The best data at your fingertips during a trigger is what the row used to be (the DELETED system table) and what the row is now (the INSERTED system table).

Kevin