Hi Hilmar!

>Invoking the RI from my own function seems an interesting alternative - but I sort of >like the idea of the RI code being maintained automatically. I think I would lose that >capability.

True. You have to watch your step. After (re)generation of RI-triggers you would have to restore the old call: CREATE TRIGGER ON table FOR UPDATE as _your_trigger(). If that is forgotten the ri code would be called twice. A bit of a showstopper...

I made a little test with a setup like "__ri_update_table() .AND. _your_trigger()".
_your_trigger() then really isn't invoked, if __ri_update_table() returns false.

That may come in handy, when you don't want to update stock, if the ri update failed. But if ri update didn't fail and your stock update fails, you couldn't roll back to the initial state.

Bye, Olaf.