I was thinking that the delete was wrapped inside a transaction (which it's not) like a Save and this would mean getting your code inside the transaction. Since it is not in a transaction and the default of a form is to immediately delete the record (TableUpdate) how do you handle cancelling the child or parent delete if one doesn't work?

Dan

>>"The thing is" (as Kevin would say) to implement it you would have to override the base framework.
>
>I can see how I would be enhancing the functionality of the base framework, but in what way would I be overriding it? I certainly don't want to 'fight' the framework.