>Thanks Paul, Kevin, David,
>
>Really bad news ! This will definitly end up in a nightmare in our case.
>Thanks for the ideas and answers, I hoped to find another idea that won't end up in building OO stuff back...
>
>But I already suggested that this will be the answer.
>
>Marcus

It really takes a transactional database for this stuff to work right, so maybe you could approach the problem the same way. Instead of using VFP's built-in TRANSACTION, you add a transaction log (eg. something like FoxAudit from www.takenote.com) and log the beginning of your transaction via some unique identifier. If all your bizobj's successfully complete there saves, you don't need to do anything special (except maybe flag the end of that transaction). If it fails, roll-back the changes by reversing the order of your transaction log (again, FoxAudit should make this pretty easy). Just an idea...