>Two items:
>
>1) SAVE TRANSACTION is not valid in distributed transactions. SQL Server will not raise an error, it'll just abort the command.
>
>2) Couldn't you check to see if the change has already been made before doing the Insert? Is there a candidate key that you could check first?
>
>-Mike

Hey Mike,

Thanks for the info. Fortunetly (for me at least) this isn't part of a distributed transaction, so it should be OK (never say never tho'). Both tables are on the the same server, in the the same DB.

Phillip