<SL> This logic will create a single record for an update, which is your goal.  

<SL> If you are seeing several log entries, the problem is with how the columns are being updated – it is likely that each column is being updated by a SQL statement, when the column value changes in the client.  This would result in the trigger firing for each separate update.

You are correct, thanks for pointing me to the tool being used by the client.  It turns out the trigger is working the way I intended.  For quick testing, I was using FlameRobin (right click on table name, "Browse data", update data in the grid, then click the check mark to post the changes).  This causes the trigger to fire for each column that is updated in a row.  When I use an update statement to update multiple columns, the trigger is only fired once per row that is updated.

Again, thank you very much.

---------------------------------------------------------------------------------

Confidentiality Notice: This message is the property of the United States Bankruptcy Court for the Western District of Kentucky. It may be legally privileged and/or confidential and is intended solely for the use of the addressee. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or taking any action in reliance on the information contained herein is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this message.