Re: triggered file list problem

["Nelson C. Smith" <ncsmith@xxxxxxxx>]

Oh, I agree with that.  The way I use that library name to protect against
mishaps is by keeping all my trigger functions in procedures in service
programs.  A trigger control file specifies the procedure and service
program to be called for each Libr/Filename combination.  So if a trigger is
fired from a file in a library from which it was not originally intended, it
will find no entry in the control file and just end harmlessly.  The control
file also makes it very easy to turn valid triggers on and off externally
without having to get an exclusive lock on the triggering file.

>
>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: david@midrange.com
+---