|
From: R. Bruce Hoffman, Jr. <rbruceh@attglobal.net> > From: Leif Svalgaard <leif@leif.org> > >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... can you do this per program or job. In many cases you may want to run the repair program in parallel with production.
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
