S
smat-consulting
Guest
Well, stick your procedure into a .i file and include it in each of the trigger procedures you want. replace with {&tableName}, and include this .i like this: { genericTrigger.i &tableName = " " } You can generate these one line trigger-files by looping through the _File table, looking for all records where _hidden = FALSE... BTW: Of course you know that it is not a good idea to have any user-interaction in a trigger (MESSAGE); I am assuming you are just using the message statement for the moment, until your proof of concept is working... right?
Continue reading...
Continue reading...