>Hi Roi,
>
>Well, if the user hits cancel in the child form, you need to revert or delete the child record. It is a pain. But I would handle it proactive.
>

Right, I just couldn't figure out how to easily revert the changes to the view without affecting the underlying tables. Jim suggested SCATTER / GATHER which will easily solve that.

Thanks.

>
>>The only tricky thing I did, and I would like your opinion on this, was dealing with the user canceling from the child form. IAW the user clicks the edit button, a new form is called (with controls bound to the dirty view's fields in the init), makes some changes (the view is now reflects those changes), and clicks cancel (I now need to change the view back to it's previous state). The only thing I could think of was to wrap the whole DO FORM in a transaction. As the transaction is only affecting the local view I don't think I will be a problem. Any comments or concerns about the transaction part?