> I am trying to envision what would have to fire in the onFocus event of the > Tab > that is set by ACTIVEPAGEINDEX that could not be done in the same code that > called ACTIVEPAGEINDEX...
Since the page is changed in a number of different places in the code, it makes sense to me that the code should be attached to the event so as not to require a redundant method call each place the page is changed. However, since that's not possible, I am doing it the way you suggest -- preceding my call to set the ACTIVEPAGEINDEX with a call to a form action to accomplish what I need to do. It's not a major deal, it just took me a while to figure out what was going on. > Also, it does seem logical that if it can't get focus (a visible=false > condition) that an onFocus event wouldn't occur.. Right? Nope. The EEP code is in the ON FOCUS EEP for one of the pages in the page control. That page is visible and I can get there with ACTIVEPAGEINDEX. The page is named (for instance) pgPage3 and the on focus EEP would, in Visual Basic, be called something like pgPage3_OnGetFocus. It seems odd to me that the page's code runs if you arrive there in one manner (the tab) but not in another manner (through code). I do recall seeing, in the most recent What's New in v79, something about this EEP being renamed, perhaps to ON TAB CLICK or something, so perhaps someone else had the same issue and reported it to RDCC. I suspect this is simply a property of the underlying Windows control and not something that RBTI could easily change. I was thrown mostly by the name of the EEP -- changing the name will make it clearer when it will fire. -- Larry
