|
Ian, I was wondering if you took Nelson's advice. I strongly recommend the buffer method. In fact I have a sample program (which I would modernize at the drop of a hat). This program reads the buffer, and updates two fields - user and date of last update - in the buffer before the record is written to disk. Just change your trigger to before instead of after and also use ALWRPTCHG. Just had a programmer here yesterday who put this into effect for a Notes application which updates a file. The trigger on that file posts the data to a more permanent file. Uses the buffer. I had to beat him into submission because he kept trying to figure out a way to read the file. But now he has seen the light. Rob Berendt ÝÝÝÝÝÝÝÝÝÝÝÒThey that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Smith, Nelson" <NSmith@lincare.com To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> > cc: Sent by: Fax to: midrange-l-admin@mi Subject: RE: SQL/400 Trigger Problem drange.com 11/15/2001 09:05 AM Please respond to midrange-l When the trigger is fired, you are already presented with the data for that one record only. Just change whatever you want to change. There is no reason to use SQL unless your change involves going out to other files for other data. > -----Original Message----- > From: Ian J. Forsyth [SMTP:iforsyth@360GROUP.com] > Sent: Wednesday, November 14, 2001 10:17 PM > To: midrange-l@midrange.com > Subject: SQL/400 Trigger Problem > > Is there a way to create a RPG trigger on a physical file and embed SQL > in the RPG code to update ONLY the record being inserted and no other? > > I know how to embed SQL in an RPG program, but if I do: > > update file x > set field Ýalue > > I believe I'm globally updating every record in the file instead of > updating > > the one that's being inserted. > > > > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. ************************************************************************************************************************************************************************************************************ This message originates from Lincare Holdings Inc. It contains information which maybe confidential or privileged and is intended only for the individual or entity named above. It is prohibited for anyone else to disclose, copy, distribute or use the contents of this message. All personal messages express views solely of the sender, which are not to be attributed to Lincare Holdings Inc., and may not be copied or distributed without this disclaimer. If you received this message in error, please notify us immediately at MailAdmin@lincare.com or (800) 284-2006. ************************************************************************************************************************************************************************************************************ _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.