×
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.
We recently discovered a situation in which data propagation triggers
were applied to several files *twice,* resulting in the data getting
propagated *twice.*
Now in this particular case, there are no other triggers on the affected
files, so it's fairly straightforward to avoid this situation.
But what of the possibility that some other application has a trigger in
the same slot? Is there a way to prevent redundant triggering, without
interfering with somebody else's triggers? I know about trigger names,
but I don't quite understand how they work, and the helptext and error
messages from my attempts to use them are rather unhelpful.
It was so much easier under the old "one trigger per slot" rule.
--
JHHL
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
