Rox,

The childBizObj references the ParentBizObj in the builder via the 'Parent Object' textbox on the Parent/Child Settings page.

I have almost the behavior that I was looking for (Page one is the list/incremental search of the Parent Object, while page 2 has the parent object controls - textboxes for now - and the container with the childBizObj and the child grid.)

The childBizObj is now being correctly requeried on new parent/requery parent
when I activate page two I can use the navbar buttons to skip thru the parent and display the children in the grid for the parent.
The childBizObj is just enabled (not checked as primary nor auto-primary)so that the childBizObj.PreRequeryHook() fires. This method contains the AddViewParameter() call with the vp and the parent TABLE'S FIELD NAME - not the parentBizObj.cUniqueIdfield. When I used the reference to the cUniqueIdField here ALL records were selected for the view; when I use the table's field reference the correct child records were selected. I have this feeling that I am somehow subverting the methodology here and that I should be using the This.obizObj.cUniqueIdfield property.
The PrimaryBizObj has both views (parent and child) set as cursors. The childBizObj has the child only set as a cursor.