Nerissa,
There are 2 properties on the form you'll want to check, nGoToPageOnSave and nGoToPageOnCancel. By default, they're set to 1, meaning focus will be set to page 1 when record changes are saved/canceled. These only work, however, if the BizObj on the page in question (in your case, page 3) has been set as the primary BizObj.

There is always one BizObj that is primary on a pageframe. Usually, it's the one used to drive the list on page 1 and it should have its lPrimaryBizObj property = .T. If you want form methods (e.g. Save() and Cancel()) to perform direcly on BizObjs located on other pages, those BizObj's should have lPrimaryBizObj = .F. (the default) and lAutoPrimaryBizObj = .T. This means that when, in your case, page 3 is activated, the BizObj on that page automatically becomes the "primary" one. Then, the form should behave the way you expect when adding/editing/canceling/saving.

Hope that makes sense...
---J


>Everything works fine. I can edit and update a record by clicking the Edit button. The problem is that if I click the cmdOkmaint button. The changes in the records are saved but I don't go back to page 1. I debug the flow and I saw that I was hitting the enabling of page 1 in SetEnabledStatus(.T.) method that is called in the saverecord() method. When the program flow goes back to READ EVENTS, I am still in page 3. Why is that so?
>
>Same thing happens when I click cmdCancel maint. The changes are not saved but I am still in page 3.
>
>Nerissa Dela Rosa
>McFadden's