Bob,

>> Anyway... I guess the answer is there is no one answer. However, you CAN code it to act the way you want. <<

>> As someone said, if
you are switching to your GrandChild view, and the parent is a new record, don't requery, just set a filter on the view. <<

Yes, this could be done as an ad-hoc thing, but I'm finding it hard to picture a general solution for an n-level heirarchy based on p-views that are then filtered. For this to work, the grandchild view would have to be parameterized on the top-level parent, then filtered on its own immediate parent, instead of simply being parameterized on its own parent. At n levels, this creates quite a bowl of spaghetti, as each child, grandchild, etc. would have to contain a foreign key to the top level. A totally general solution allowing an n-level heirarchy to be handled in any situation would require each child table to contain a foreign key to every table at every level above it. The troubles multiply geometrically.