I don't understand why the execution order of UIEnable is a problem.

Is it the fact that it fires for objects on the first page at initialization?

Is it the fact that if fires AFTER the Activate/Deactivate?

Or is there something else I'm just not understanding?

and I cannot duplicate the firing of a page.Deactivate() during the Initialization process.

Although, I do notice that if I
select Page1.Text1,
then click on Page1's tab (not the page interior, but the tab, and only if I click with the mouse),
that the Deactivate/UIEnable[s] fire and the Activate/UIEnable[s] fire.
Is this the problem?

>Hi Trey,
>
>>UIEnable works as designed.
>
>Then for you any sequence is good.
>
>On VCX Form , a Pageframe initialization is
>uienable(.T.) for every control on page
>....
>Activate the page
>
>**************************
>
>On Form SCX Form , a Pageframe initialization is
>Deactivate the page 1
>....
>Activate the page
>
>and none uienable
>
>**************************
>
>On PageFrame showed
>
>Activate the page
>uienable(.T.) for every control on page
>
>**************************
>
>For me this is a permutation of events.
>
>Fabio