Nelson, >This also creates the "gotcha" that when you duplicate a file into a test >library, for example, it also duplicates the hard-coded qualified trigger >call. Then running test data through it in your test library fires your >production trigger. Be careful out there. And if you use CPYF ... CRTFILE(*YES) it won't even duplicate the trigger events at all (although CRTDUPOBJ will). Being careful is always good advice. Having the trigger program from the production library being called is not necessarily a problem, depending on how the trigger program is coded. But that is partly why I said you could/should examine the library name passed in the trigger buffer if you are accessing other objects. Triggers are a wonderful addition to our arsenal of methods. Doug +--- | 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: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.