I need to setup a cBizObjMaintenanceForm where the grid on page 1 is linked to a read-only view and page 2 is linked to a updatable view. I am using SQL Server as the back end. My users want to see all the records in a table that could have many entries. I want to limit the grid listing to only pull from SQL Server the fields I need for the grid and the primary keys. When the user selects the record to edit and goes to page 2 then I want to requery the updatable view with the promary key and only pull one record. This will increase the speed of the entire form and keep the users happy.

Here is my dilema, I changed the CListOneToManyObj1 to be set to AutoPrimary and then setup another Object on Page 2 and set it to AutoPrimary. This works at setting the oBizObj as the user goes to Page 2 and back to CListOneToManyObj1 on Page 1. However, when the user clicks the delete button on Page 1 the framework wants to change the oBizObj back to CListOneToManyObj1 which fails to delete.

Is there a place to tell the framework to use a Bisiness Object for all the data updates? This would make this so much easier. I am finding I need to add code to overwrite the framework logic in many places which concerns me.

Can CListOneToManyObj1 object not be the primary object? When I tried this my form did not work right.

Any insights to this would be great. TIA