Tracy,

Crazy idea...in Page1, can you set a *property* of either the form or the page frame to the desired value of your field on Page2, and then update the Value property of the field on Page2 from that property while in the Activate method of Page2 (which would mean that it would populate the next time the user selected the page) ?? This would eliminate your having to address the control directly while you were on Page1, and therefore no longer having to worry about that control "bleeding through".

And don't pull your hair out -- I've already tried that, and it didn't help (bg)...

Evan

>I can't do that because a timer runs which has to update controls on page 1 and this happens even when other windows are active. If the timer clicks in while the lockscreen is in place I'm afraid the user may not see critical notices created by the timer that must be displayed.
>
>
>>I have 3 pages on a pageframe. When I am updating data on page one, a form method is run which then updates a field on page2. The form method is called in the lostfocus (tried valid as well) of the field on page1. After the field on page2 is updated programmatically, focus is still on the field on page 1 but the editbox (field on page 2 that is updated programmatically) bleeds through to page1. Actually not the entire editbox, just the scrollbars in the editbox for some reason. Now on page 1 sits some shapes and field on page1 which the user is actually typing in, sits ontop of that shape.
>>
>>I have tried:
>>
>>Putting a shape or container ON the editbox on page2 and only hiding it when page2 is active
>>setting the editbox.visible to .f. unless page 2 is active
>>setting both the zorder() of the editbox (to 1) and the shape or container (to 0) unless focus is on page 2
>>Changing the way the value in the editbox is updated - using the field in the table or the control on the form...
>>
>>I have tried messing with zorder(), visible, the covering shape, the box itself all from refresh of the editbox, editbox programmatic change, activate and deactivate of the page, et al
>>
>>Any ideas? I'm ready to pull my hair out!