>> WITH Thisform.PageFrame1.
>> .Page1.Refresh()
>> .Page2.Refresh()
>> .Page3.Refresh()
>>ENDWITH
>>
>> or
>>
>>Put This.Refresh() in the INIT Event on each page
>Plinio,
>
>The Init won't solve this problem as it only executes once when the page is created. There are tow ways to solve this problem, either put THIS.Refresh() in the Page's Activate event or create a class that has THIS.Parent.Refresh() in its UIEnable event and put one on each page.
>
>The problem with refreshing all the page's from the fomr is that VFPO doesn't do this to save time. The user cna only see one page at a time so only refresh the page they see. When they change pages refresh the new one.

My concern between updating them all at once and one at a time is user perception. If each page takes 1 second to update the data behind the page, I don't want to have to update every time the user changes pages. Nor do I want to update them all in a 9 second block.

If I place the refresh code into the activate method, then the user gets a one second delay per page, every time they switch pages. (Even back and forth) If I place the refresh code into the refesh of the pageframe, they take a bigger hit once, and can swap pages freely. Of course there are tradeoffs to it all, maybe thats why MS decided not to refresh the pages themselves. ;)

Ultimatly, I would like to have a subclass of a page that has a "needupdate" flag that the pageframe can set so only the first time the form activates, it refreshs. So the user only waits for what they want to see, once.