|
Absolutely Nelson. Thanks for saying that so kindly. I even went back and looked at my sent mail because I can't believe I typed "*NO". It took a long time to learn about that parm. Pete Hall finally set me straight on it a couple of years ago. I will admit to not understanding it though. Since we are only changing the buffer and not the record why does the database care? And why not just always set the parm at *YES? What is the downside? What protection or efficiency does it provide? _______________________ Booth Martin boothm@earth.goddard.edu http://www.spy.net/~booth _______________________ "Nelson C. Smith" <ncsmith@gate.net> Sent by: owner-rpg400-l@midrange.com 01/24/2000 11:14 PM Please respond to RPG400-L To: <RPG400-L@midrange.com> cc: Subject: Re: Data base triggers All except the first one. I'm sure Booth meant to say *YES. ----- Original Message ----- From: "Jim Langston" <jlangston@conexfreight.com> To: <RPG400-L@midrange.com> Sent: Monday, January 24, 2000 9:09 PM Subject: Re: Data base triggers > Okay, now I'm confused. Here are a number of replies: > > "Martin, Booth" <BoothM@goddard.edu> Wrote: > Yes you can update the record with the trigger program itself. > When you ADDPFTRG use: > Allow Repeated Change . . . . . *NO > and make the change to the buffer *BEFORE the *INSERT or *UPDATE. > > Scott Mildenberger <Smildenber@Washcorp.com> Wrote: > This is possible, we have a lot of triggers that do at this. You just > change the field in the after buffer in your trigger program. When you add > the trigger to the file, the trigger time must be *before and the ALWREPCHG > must be *yes. > > Hartman Richard <richard.hartman@brctsg.com> Wrote: > We have triggers that default fields if they were not entered, which does > not cause the trigger to fire again because the trigger is already editing > the fields. > The trigger only fires once per record when executed, so on the record that > was changed, anything the trigger does will only occur once after it is > triggered. > > Which of these is "right"? Or are they all? > > Regards, > > Jim Langston > > +--- > | 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 +--- +--- | 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-2025 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.