S
smat-consulting
Guest
Not sure I understand exactly what you are trying to do. Want to explain a little more? As a basic guideline, NEVER use any user-interaction (message, display, pause,...) in a trigger. User-Interactions should be in the part of the program that deals with user-interface. That part shouldn't have database access. That way, you can always add a different user-interface to the same backed, or exchange somethings on the backend without interrupting the user-interface... I use triggers almost exclusively for data-integrity checks (see if foreign keys are valid, disallow delete if dependent record still round, cascade delete children with parents, and such). Whenever I did something else within the triggers it came back later and bit me in my seat-cushion 
Continue reading...
Continue reading...