>Hi Ed,
>
>It sounds like the parent-child relationship might not be set up properly between the bizobj on page1 (the parent) and the bizobj on page2 (the child). Consequently, the child object is not being requeried when you want. Here are some suggestions:
>
>1) Make sure the view you created for page2 is working properly by USEing it in the command window.
>
>2) Make sure there are no typos in data environment class and the dynamic view cursor class.
>
>3) Once you've checked for the easy stuff :) look at the business objects.
>a) In the parent bizobj on Page1, make sure you have the cUniqueIdField property set to the name of the primary key field.
>b) In the child bizobj on Page2, make sure you set the cParentBizObj property to the name of the parent bizobj on page1, then make sure you set the nRequeryType property to 1 - requery when parent changes.
>
>4) In the PostInit() method of the child bizobj, make sure you properly setup the aViewParameters array property. Refer to the section 'Specifying and Creating View Parameters' in the MM Developer's Guide.
>
>HTH
>
>George

Hi George,
I've done all of your suggestions, using the MM Developer's Guide (Guide? more like Guess How Guide) I created the view parameters for the aViewParameters array property. Now I get two errors #1) VPARM_NAME is not found, if I ask for the debug window and step out I get error #2 VPARM_EXPR is not found. If I step out of that error, the form comes up. However, it runs soooo slooooow it takes a 15 - 20 seconds to arrow between records on the first grid. If I change to page 2 I am asked for the paramater for the query. I can enter in a valid number and the grid on the second page does fill :), but it also is slooow.
If I choose not to open the debug window on the errors then I get a VFP error and it shuts VFP down.

Ed