>>So your users click "Close" and the data is assumed saved?
>
>No, because the data is not saved. The changes are held in the buffer, however. This is my point- you really shouldn't give a user an indication that data is saved if it isn't.
>
>>What if they don't want the changes they did to the child? Do they have to cancel the parent to cancel the child changes then go back and edit the child again?
>
>They can do either way. They can reopen the child form and cancel individual child records or they can click the cancel button for the parent which blows away all changes to parent and child.


I really don't like that. With your method there is no way for the user to recover from a mistake. A user could have edited a record on form and clicked close on the child. Their data is good at this point. Now before the table is updated they go back to that same record and edit it again. Now they realize they made a big mistake and what was entered first was right. It's all gone now though now because if they click close again the buffer is updated (not the table) and if they click cancel the table is reverted back to it's original state.