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

I even put a whole block of code into our QuestView product, just to catch exceptions thrown by triggers, and convey them to the user as politely as possible.

And as to "bounceback" or "boomerang" effects when triggers are used for data propagation (something I have some experience with), it's generally good practice to design the triggers so that if an "outbound" data propagation (whether by trigger or by something else) trips an "inbound" propagation trigger, the "inbound" trigger recognizes what tripped it, and quietly exits without doing anything.

--
JHHL