Help - Triggers vs. Batch processing, LARGE DB.

Does anyone have any experience in using Triggers (and stored proceedures) in the database for updating and transferring the data between tables and external applications? Our current system incorporates a series of background processes which scan various tables to perform this very function. I am concerned with the OnLine 5.02 engine being able to use a C based program from within the Triggered event. Has anyone done this? Have you compared the overhead against background 4GL applications? Have you used it in a busy OLTP environment against a Large database? My feelings are that the Triggers would be the most efficient way to get the data to the next table (after updating it), but I don't know if the OnLine engine can pass it directly to an ESQL/C based program. Does it go directly? Does the 'triggered' program need to query the table to get the info? I would be pleased to hear of anyone's experiences and I will summarize the information and distribute it to Kerry for the Informix FAQ. As this type of programming has been implemented throughout the system it could greatly enhance the operation of the system. Thanks in advance. Albert E. Whale aewhale@emi.lm.com ---------------------------------------------------- Sr. Systems/Database Consultant Executive's Monitor, Inc. 1789 S. Braddock Ave, Ste 220 Pittsburgh, PA 15218-1868 (412)243-4600 Fax: (412)243-4830