Constraint Checking w/triggers & logging

We are using Online 5.01 triggers to prompt other processes to update the databases they maintain either in memory or flat file. The problem is, since we have transaction logging, the constraints aren't checked before the trigger calls these processes. (i.e. the process doesn't really know if there was a change or not) Page 2-30 in the Using Triggers guide seems to address this issue, but the solution doesn't seem to work for me. (i.e. I put a statement in to check for the appropriate constraints within the trigger statement, and it still doesn't seem to catch it.) I have a call into Informix support, but it's taking a while. Can anyone out there shed some light on this situation? Note: The trigger actually calls a stored procedure which in turn calls the specified process. I suppose I could check this in the stored procedure, but right now we have one stored procedure for 50 or so tables we trigger off of. If I did it within the stored procedure, I'd have to implement 50 or so different ones I think. Please post all responses to this thread. Thanks in advance, Julie C. Jumes