When modifying tables and triggers, it is best practice to keep custom code of any type, SQL or vb, as separate from the standard SAGE MAS 500 source as possible.

When adding custom triggers to tables, because the stock triggers are not ordered, I continually have to make sure that I set mine new custom trigger to fire 'LAST' with the sp_settriggerorder procedure. SQL Server by default fires triggers in no guaranteed order and has options for First|Last|None.

My guess is that the stock triggers ought to always fire first to preserve RI in the DB and any custom triggers ought to follow. In order to accomplish this easily, we need only to specify that the stock triggers fire First.

by: Matthew A. | over a year ago | 5 - Integration