|
Thank you. That seems like the right solution. I appreciate it. I had looked at it, but turned away because it required hard-coding column numbers, so far as I could see. I was afraid someone would find out about it and report to everyone here that I was hard-coding column numbers, and I would be humiliated before my peers. In <35986717.111D@gate.net>, on 06/30/98 at 12:18 AM, Nelson Smith <ncsmith@gate.net> said: >If you use the "Before" trigger rather than the "After" side, you will be >looking at the actual record data that is about to be updated. Just >change the fields to whatever you want them to be (in the "after" part of >the record parameter that comes into the trigger). Then let the record >update normally. >Note: this requires you to use the Allow Repeated Change option on the >ADDPFTRG cmd. -- ----------------------------------------------------------- boothm@ibm.net Booth Martin ----------------------------------------------------------- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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.