You can still use multi-page form, however you have to add 2 custom properties:
1. Parentprimarykeyvalue
2. Childprimarykeyvalue
Correspondingly, each Page.Activate event should move record pointer based on this property values to restore 'last' entry situation.

>Sorry my response took so long...but I am still trying to figure out the LIVE version of UT and the Navigator. The latter does not seem to get the whole thread...unless I hunt for it.
>
>In any case, we pin pointed the the problem...at least here.
>
>We were using two pages on one form. The customer would select new company ABC Co. on page one. This would create 1 parent and 1 child record with the same ID. The customer then goes to page 2 which is an active browse of the whole data file (for the purpose of editing or changing an existing record) and highlights XYZ Co. (This was moving our pointer). When the client then goes back to Page 1, even a form refresh doesn't solve the problem. The parent and child have the same customer ID, but the child now has a Customer name of XYZ.
>
>While I am sure this is our coding problem...as we all learn Visual Fox (there are three of us here)... we will solve it by making two separate forms.
>
>Form 1 will be for ADD, Form 2 will be for Edit and Delete.
>
>Thanks for all the feedback.
>Glenn
>
>>Good point, Nancy. I always forget this, since my save buttons are form-based not toolbar-based.
>>
>>Barbara
>>
>>>Could this be due to the situation where the cursor is in the control, a toolbar button is clicked to save, and, since the toolbar never receives focus (therefore the control never looses it), the controlsource isn't updated? Could I put another clause in that sentance? *g*
>>>
>>>...snip
>>>>Are you using private datasessions? If not, another form may be moving the record pointer. If you are, then check to see if you've moved the record pointer in any fashion. Do you have relations set? They often will move a child record pointer.