Re: Anyone using Triggers to enforce data validation & business rules?

Thank you for your detailed reply, Buck. I agree with the idea of
using a "Trigger Mediator". I would send *ESCAPE message from the
Mediator rather than the "Trigger Handler". But I would only use an
*ESCAPE message to STOP an Insert/Update/Delete and flag an error
condition - not to communicate with a previous call-stack entry.

Too many opportunities for the call-stack to contain something
different what your Trigger Mediator or subsequent Handler might
expect.

Did you have a chance to look at the Data export example in my
previous message? Error handling would be simpler, and the interface
would be bullet-proof.

In the Trigger Handler:

if trg.aft.email = *blanks; // user didn't fill in an email account?
trg.msg.type = type_error;
trg.msg.column = 'EMAIL';
trg.msg.text = 'Please fill in an email address, which is a required field';
trg.esc = *on;
return;
endif;

In the Application:

write(e) myrec;

if %error() and trg.esc;
... process trg.msg values (ie. show error on screen)...
endif;

...

No messy call stacks to deal with.

HTH,

Nathan.