Hey Fabio,
Thanks for the input. I will give it a try. So far I have found a work-around, which is just to use a stored proc instead of a trigger. That seems to work fine, and it does not have the 'Exception_Access_Violation' problem like the view trigger when trying to update a previously existing entity. (see Exception_Access_Violation thread in 'SQL Server in general' section).
Thank You
Rollin Burr
Politicians and diapers have one thing in common. They should both be changed regularly, and for the same reason.