>No, this is a bug into the form, it call Pf.page1.Activate before Form.Activate
>
>try1 ( this remove the TAB done before the controlsource eval )
>

>*  put this in Form.gotfocus or Activate
>CLEAR TYPEAHEAD
>

>
>try2: this send the bug into a zombi pageframe
>* but you have not a Activate on the true pageframe
>

>add a empty pageframe ( no pages ) with Visible = .F.,
>and "send to back" it ( it must to be the first control on the frame )
>

>
>try3: this delay the Controlsource eval
>

>* set BindControl=.f.
>* add this into gotfocus
>thisform.BindControl=.T.
>

>
>We are making a slalom among the bugs.

I'm not that kind of mazochist (? spell) :) I already played with all these things trying to make everything work. My final solution is to have pageframe with 0 as ActivePage in design time and set ActivePage to 1 in form's Init in the run-time. Therefore I execute Page.Activate only once (though may be prematurely) and don't have set focus problem. My combos are also working (fingers crossed). So I let it rest for some time until I decide to re-try your keyboard idea again and apply all other various gimmicks.

My manager thinks, that Activate on the same page Click and left-right arrows behavior bugs are not that important for the moment and we're going to live with them. I'm still thinking of designing my own pageframe class or picking up some of the correctly working class...