That's why we will look at the file library in the trigger parms, It can save your butt. All our production data is in a few libraries. -----Original Message----- From: Nelson C. Smith [mailto:firstname.lastname@example.org] Sent: Thursday, October 28, 1999 7:15 PM To: MIDRANGE-L@midrange.com Subject: Re: triggered file list problem 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. +--- | 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: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.