|
-----Original Message----- From: Leif Svalgaard <leif@leif.org> To: midrange-l@midrange.com <midrange-l@midrange.com> Date: Monday, August 20, 2001 12:28 PM Subject: Re: triggers within commit cycles >There is a simpler (better?) way of doing this: >Have an access module for every file or table >you use. Place the business rules in the module >(could even be turned on/off by a switch in the >calling sequence - sometimes you don't want >any rules, e.g. during emergency repair of >data in the file). but now in 5.1 you can suspend the triggers... =========================================================== R. Bruce Hoffman, Jr. -- IBM Certified Specialist - AS/400 Administrator -- IBM Certified Specialist - RPG IV Developer "America is the land that fought for freedom and then began passing laws to get rid of it." - Alfred E. Neuman
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.