Rex,

Thanks for the response. The client wants the navigation controls to operate the GridList, even when editing a record on another page. So it appears that I have to make the GridListBizObj primary. If I make the "edit" bizobj a child of GridList, it doesn't pass thru the commands to "prompt to save," do the save, etc.

Currently, I have put code in the GridList obj that passes through the method calls that should operate on the editable BizObj, while handling navigation calls itself. It's a lot of work.

I do appreciate any suggestions.

- Bruce

>Bruce,
>
>You probably need to change the PrimaryBizObj, using the SetPrimaryBizObj form method, to the page business object to get this type of functionality.
>
>HTH
>
>Rex
>
>>My question concerns how to set up business objects in a particular form setup.
>>
>>My form is a subclass of cBizObjMaintBaseForm. Page1 ("List") contains a grid and query parameters. When a user presses "Fetch", SQL Pass thru returns a cursor to populate the grid with 2-3 columns from the table in question. The user navigates to a row in the grid, then clicks on Page2 to edit. Page2 requeries the remote view to fetch the row to be edited. In other words, the grid uses one cursor, while controls on Page2 use a different cursor.
>>
>>The problem is getting the navigation controls to navigate through the grid, *and* to communicate with the BizObj on Page2. It seems to me that navigation calls (Top, Next, etc.) should go to the grid's bizobj, but that file operations (New, Save, etc.) should operate on the *other* BizObj - on Page2.
>>
>>Please let me know if anyone has a solution to this sticky issue. It's one of those situations where I feel like I'm fighting against the framework!
>>
>>Thanks in advance,
>>
>>Bruce Allen
>>Left Brain Incorporated