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.

If I delete the according record in Table1 my Table3-Code fires, but the record pointer of table3 stands anywhere? So I can't find out wich record is planed to be deleted, so I can't perform my action!

Is this a known issue. I am really confused, because I never ran in any problems like this ? Perhaps our RI Code is not OK ? Any ideas ?
Marcus