× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. May 2002

Triggers: using the same program for both *BEFORE and *AFTER

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Are there any issues with using a single trigger program for both *BEFORE
and *AFTER event processing (with trigger program logic controlled by the
value of QDBTT)?  I’m not trying to do anything weird from a timing or logic
standpoint: I know the program will be invoked twice (causing some
additional overhead) and I doubt you can count on a record’s *AFTER
transaction immediately following the *BEFORE transaction.

Thanks,
Reeve
--

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.