Sorry, SQL Server 7 doesn't have that and I've not heard about anything on those lines in SQL Server 2000 (unless you write your own function called TriggerEvent < s >).

In your design, do you have to incorporate all trigger functionality into one trigger? Or can you separate it into multiple triggers, each called for the individual purpose (insert, delete, update)?

>Larry -
>
>thanks - that is (sort of) what I'm already doing - I was hoping for a simple function along the lines of "If TriggerEvent() = 'Insert'"
>