Thanks for that heads-up...

But what I'm doing is a

select full outer join, so I can get all records inserted or deleted and process them and by NULL, I can detect for the insert / delete and process accordingly...

Anyhow, I guess that makes some sense, but seems strange if your doing a single update command and updating 5+ fields that it would trigger each time through.

Anyhow, its working, and we have that task under control.... Thanks all





>Hi, Don,
>
>One other thing to take into account, in your testing...
>
>SQL Server insert/update triggers fire ONCE per insert/update statement, regardless of how many rows are affect. So if your single UPDATE statement affects 5 rows, the trigger fires once, with 5 rows each in the insered/deleted tables. You may already know this, but wanted to mention it anyway. (Some people code triggers on the assumption that only one row will be affected).
>
>Kevin