|
Triggers-- more than stuffed, dead horses!The only problem with placing the trigger is that both the file and the trigger program need to be in the library list any time data in the file is touched.
In our case, we have the trigger and program in different libraries. The only problem this causes is when I have to use DBU to make an 'emergency' patch to live data-- if I forget to add both libraries to my library list, the data may be changed, but the trigger will fail and the triggered function will not be performed.
I don't know if placing both the trigger program and the file in the same library would help-- the library would still have to be in the library list, and if I forget... the same problem would occur.
If I'm using SQL to make a mass change, if the trigger program is not in the library list the first record is changed, the trigger fails to fire, and the SQL task stops with an error message.
The choice is still yours! (: --Paul E Musselman PaulMmn@xxxxxxxxxxxxxxxxxxxx
I have seen threads on triggers where it is said that it's best to put them in the same library as the data files, and others where this is discouraged. In order to allow us to make a decision, I'd like to hear advantages and disadvantages from either point of view. Peter Colpaert
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.
midrange.com
