>Hi,
>
>this is a Old Bug ? I see this on VFP6/7/8.
>
>On a VCX, a pageframe initialization events is:
>

>Page1.Init
>....
>PageN.Init
>* Now ActivatePage property is read
>* On any control on ActivatePage
>Uienable(.T.)
>....
>Uienable(.T.)
>Pageframe.Init
>.....
>Form.Init
>pageframe.ActivatePage.Activate
>Form.Activate
>.....
>

>I aspected
>

>Page1.Init
>....
>PageN.Init
>* Now ActivatePage property is read, but not events fire
>Pageframe.Init
>.....
>Form.Init
>pageframe.ActivatePage.Activate
>* On any control on ActivatePage
>Uienable(.T.)
>....
>Uienable(.T.)
>Form.Activate
>.....
>

>
>On SCX UiEnabled not fire, not before, not after;
>instead fire a Deactivate of the default page.
>
>Then, is hard to build a general pageframe, good on SCX and VCX.
>
>Fabio

No it's not an old bug because it's not a bug.

From help as is :
"Parameters
lEnable
Contains a logical value that specifies whether the page that the object is contained within is being activated or deactivated. If lEnable is true (.T.), the page that the object is contained within is being activated (becoming the active page). If lEnable is false (.F.), the page is being deactivated (becoming the inactive page).
Remarks
Use the UIEnable event to specify any action you want to occur for an object or control when the page that it is contained within is activated or deactivated.

The UIEnable event does not occur for pages when the form is initially activated. The UIEnable event occurs only when a page is programmatically or interactively activated or deactivated."

Cetin