Hi Trey,

Good splitting questions, very well.

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

1. Because on Activate of page i have code for workaroud the PageOrder Bug,
and setting other page property, read by control on page when UiEnabled is fired.

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

2. This does not respect the documentation
3. Read point 1.
4. But it not fires on SCX.

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

5. I want this; on Help is writed :

"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."

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

6. AFAIK, no.

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

7. I write a repro code ( i test with pageFrame and MemberClass )

>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?

8. No, this is not a problem ( now ). It is good because Deactivate support NODEFAULT.

Fabio