>>What does you Save button do on the Child form? Does it tableupdate the child or simply closes the child form? If the former, than your Cancel button would work just fine in your scenario.
>
>The save button on the child would just close the form (and run the record validation). I do not want to tableupdate the child. That is handled when save is clicked on the parent form. If cancel is clicked on the parent I expect the changes on both the parent and child to be reverted (which is easy to do with tablerevert).

Yes, that's the exact scenario we dealt with about two + years ago. I do remember we used SCATTER NAME methodology, but don't recall details right now.

I may ask my former colleague to check details of the implementation later on, need to run now.