Re: Trigger Program

[DAsmussen@xxxxxxx]

Jeff,

In a message dated 12/28/99 1:29:19 PM Eastern Standard Time, 
jlcrosby@fwi.com writes:

> The idea is, since it's a trigger, it's a part of the database and not
>  the application(s).  Multiple sources could be dumping the records.  And
>  yes, each source could execute a single command as the last step (after
>  dumping in the records), but then it's the application(s) doing it, not
>  the database.  Or I could write a program that goes to sleep and checks
>  every X minutes for new records, but then a separate job is active just
>  for this purpose.  Same thing with using a data queue.
>  
>  It's not a big thing that I'm dying over, it just seemed a useful thing
>  to me. 

Ahhh, cross-platform application implementation.  Now _THAT_ I understand!

Thanks!

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com

"I'd rather be a failure at something I enjoy than a success at something I 
hate." -- George Burns
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---