×
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.
On 9/22/14 7:54 AM, rob@xxxxxxxxx wrote:
You write a database tool, right? What would be a best practice for you
on having a trigger throw an error that your utility could handle it?
Speaking only for QuestView, any trigger error in an insert, update, or
delete operation (including the trigger program itself failing in some
way, e.g., a level-check error) that throws an escape should, at least
so far as I'm aware (and I wrote the code) be handled by QuestView, and
reported back with a "Change vetoed by trigger: &1" message, where &1 is
the actual escape message sent by the trigger.
--
JHHL
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
