>Hilmar,
>
>thanks a lot for your answer, somtimes it really helps to go one step back,
>or write a question on UT to get around not seeing easy things.
>
>>Why do you need to mess with the RI? Usually, you can just add functions like this:
>>If your RI-code is: __ri_MyTable_Update()
>>You convert it to: __ri_MyTable_Update() AND MyAdditionalFunction()
>We already tried your solution quite a while ago and ran into the following problem: This works fine as long as the trigger is called directly. Lets say you habe 3 tables: Table1, Table2, Table3 wich have RI for cascading delete.
>
>The __ri_MyTable_Update() of Table3 works fine when I delete a record in Table2. I get into my code and have the record wich is planed to delete as actual record.
I would use the PK of the originating table (the table for which the trigger is defined) to do additional actions when deleting a record. Your custom code would search for records that have the same FK.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
