|
By any chance have you set the trigger to fire *AFTER instead of *BEFORE? You need to change the buffer *BEFORE you *INSERT/*UPDATE the record. _______________________ Booth Martin boothm@earth.goddard.edu http://www.spy.net/~booth _______________________ JFinney@omnia.co.za Sent by: owner-rpg400-l@midrange.com 01/20/2000 08:48 AM Please respond to RPG400-L To: RPG400-L@midrange.com cc: Subject: Trigger Program Prb Hi All, I have a small trigger program which is set to intercept any *INSERT 's on a particular pf. Now the pgm has no problems receiving the data through the buffer which is passed to it. The problem here is that when I run the trigger pgm in debug, I watch the buffer values change (which is what I want the pgm to do) then after the pgm has finished running and I check the file, the previous (undesired) values are in it. Is this buffer merely a copy of the original record to be inserted ? Perhaps from my explanation you can tell I'm new to triggers and the 3 examples in the Library Reader update/write to other files and NOT to the record itself. I really am pressed for time now so any help forthcoming would be appreciated. Regards John. +--- | 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 +--- +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.