Hi Paul,

>It really takes a transactional database for this stuff to work right,
Or just not working with views...

>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...
Thanks for another idea. My problem is in fact much bigger because we need to do tests (simulation) on a big variety of actions (that can be done over existing bizobjs) just to get a failure log, without really performing these things. There it is nearly unpossible to record all changes that will need to be set back. I will sleep another few night over this problem and perhaps have to discuss this feature with our customer....

I will thing about the FoxAudit idea. Another big thanks for the ideas !!


Marcus