9011 and 9014 don't trigger off of the same table..are you sure that it's not 9015 and instead of 9014?
The trigger process searches for required updates from newest to oldest..then applies from oldest to newest.
Since update 9015 'assumes' that 9011 is in-place, and that it is possible for that case not to be true, I added the 9016 query.
If 9014 isn't triggering the first time around..but, is on the second..I'm not sure what's going on there.
EDIT:
Oh, I see now..I was stuck on the issue that someone else reported..and 9016 should fix that.
Yes, I do see where 9010 and 9014 are tied..lemme look at that now.
__________________
Uleat of Bertoxxulous
Compilin' Dirty
|