Never having learned much more coding than RPG 2, I guess I was hoping
for a simple way to trigger just a CLP - which would probably contain a
query or two which would "select" out only the records for the vendor in
question, and only those which have been changed or added since last
"trigger". Then, probably an auto PC support download, and an email
with attachment out to the vendor. I had these visions
..................

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, April 26, 2007 12:28 PM
To: Midrange Systems Technical Discussion
Subject: RE: Brainstorming

Yes it should "be work". But it won't work. :-)

When a trigger is fired many parameters are implicitly added. Including
such information as to what file, in what library, was updated. Also
what the record format look like before, and after, the change. That
way you can automatically do stuff like "I only care if they changed
certain fields on the PO. Like, if they changed the shipping address I
could not care. But if they changed the status to say shipped I want to
send a notice to the customer that it was shipped at this date/time on
this truck.

Now, with all the parameters automatically sent to the program you
should NOT chain back to the file that the trigger was based on. Why
would you have a need to? All the information is in the parameters.
Unless you are doing something really weird like sending the customer a
list of, not only this po, but all po's they have with you.

(As I am typing I just realized that I am confusing PO's, customers and
vendors - try to get past that.)


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.