>Hi Ed,
>
>>Better, change the .Default property of the button as appropriate - set it true in the page's Activate event, and .f. in the page's Deactivate event. this would allow each page to have its own .Default action
>
>How come Button.UIEnable doesn't work? You'd think it would.
>

I don't see a corresponding event that fires when the container deactivates. It also doesn't fire the first time the page is activated if it happens as a result of the form's initial activation.

>This.Default = lEnable