>I hope someone has some ideas or experience with this kind of problem. I am trying to create a Parent to Child to Grandchild relationship within a form. I was able to set up this relationship on one cbizobjmaintenanceform. Page one has the parent properties, page two has the child records list, page three has the grandchild records list. Page 3 is disabled until a record is added to the child list. Everything is fine if I add one parent record and have one child record and one grandchild record. But if I add a parent record with a related child record and then add a grandchild record and go back to the child record list and try to add another grandchild (all before saving the parent record) then I get a message that says there are uncommited changes to the grandchild view file. It's not that I don't understand the problem. I see what it is trying to do, the grandchild view file is trying to requery but the changes made are not save yet. Is there some kind of solution to a
>successful parent, child, grandchild type of relationship?


As someone new to the MM framework, I just solved this problem for my own application -- though I don't know if my solution is the favored one. I created a query which includes all the grandchildren of all the children, and set it up as a direct child of the parent. Then (in the activated page of the grandchild) I added a filter which limits the visible records to only the grandchildren of the current child records. Thus requerying is done only on a new parent.

Anyone with a more elegant solution please chime in.