Re: Trigger question

["Alan Campin" <Alan.Campin@xxxxxxxxxxxxxxxx>]

> Seriously, I've also been sorely tempted to put surrogates in on not 
> only my workflow trigger but "inbound interface" triggers, but worry 
> about the overhead of an additional call, particularly when the
trigger 
> program itself is sufficiently big and complex to affect performance.


I did not see your original post but I assume you are talking about
using a Trigger Mediator. 

If you go to www.think400.dk/downloads.htm and look for Trigger
Mediator, you will find a complete trigger mediator that lives between
database and your program and it is written as a service program to
reduce overhead.

The only caveat I can offer is that it will not work if you are doing
recursive calls. (Your trigger program fires another trigger call). I
need to get it modified to use a small piece of "C" for the program
entrance to handle this but have been too lazy to get it done. 

In any case, it is a complete piece of code with screens to maintain the
database of tables names and service programs to call.