|
I am attempting to get our triggers under control and have run into what I *think* is a problem. It has to do with record locks, and the discussion we had recently which also included a record lock discussion, didn't seem to answer my question. We have an order entry program that updates/adds to file OETITLP. This program ALSO updates a file OESECTP. OETITLP has a trigger attached that ALSO updates OESECTP. I believe this is causing a lock issue when the trigger attempts to update the SAME record in OESECTP that is updated by the program. It seems to be that a trigger should not be updating a file that is being updated by a program that triggers the trigger. Or, maybe, the trigger needs to be smarter and not run when the trigger is triggered by said program. Is there a SOP for this? Thank you, Dave 642-371-1163
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.