>I have a form with a parent-child-grandchild relationship. Different pages of a pageframe work on parameterized grandchild views, and I'd like the ability to save/revert changes to all views at once. But the Mere Mortals framework discards changes upon requerying business objects.
>
>I've got two ideas that might make this work, but both seem ugly: requery and present filters instead of views, or create secondary views that update the primary. Which one should I use, or is there a better option?
>
>I don't want to break the grandchild relationship out into a separate form - part of the design goal was to collect this data from ten screens to one.

I don't understand the problem exactly here. Why you can not have 3 related biz objects with appropriate properties for the child objects (Save on Save parent, etc.) ?