>At that point I must commit and requery the grandchild view.

I understood and agree with everything you said except this. Why do you have to commit and requery the grandchild view to add a second child?

Because you're only showing the children (grandchildren table) of the currently selected record in the child table?

If that's the case, I see no problem telling your users at the point of trying to add the second child: "you have to save the parent, the first child and the grandchildren before creating the second child." (Worded differently, of course.) "Do you wish to do this?"

If they choose not to do it, don't create the second child.

Naturally you shouldn't save anything "behind the scenes" without telling the user about it. But there's nothing wrong with requiring one action to be completed before another takes place, as long as you let them know it's going on.

All my opinion, of course.