|
What happens if the change is made *AFTER? Or, if there are two programs, one *BEFORE, that sets a flag announcing the need to run the 2nd program at *AFTER? In <199810241445.KAA14580@lucas.emi.com>, on 10/24/98 at 10:42 AM, "David Prowak" <prowakd@emi.com> said: >Hi, >I have a MASTR_FILE that has a trigger attached to it. It's a *BEFORE, >*UPDATE trigger, allowing repeated changes. Under certain >circumstances, when the master record is changed, I then need to make >changes to 4 other records from the MASTR_FILE. >So what happens is that when I go to change the 1st of the 4 records, >the trigger program is called again, and I get an error because of the >recursive call. >How should I handle this situation? I really want to define the business >rules for >this application in the DB, but I'm stuck. -- ----------------------------------------------------------- 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.