The scenario is that the base view of the table has 2 INSTEAD of TRIGGERS; one for INSERT and the OTHER for UPDATE.
The AFTER TRIGGER resides on the base table but when data is INSERTED, it encounters a SQL Error (I'll post the exact error shortly)
I've just specified that the AFTER TRIGGER fires LAST (SP_SETTRIGGERORDER) and I'm currently testing it.
I'll let you know if that works.
A Program is only Complete when the Programmer Dies