>Dragan,
>
>I am so close on this I can taste it... The only remaining problem I have is that I have my calls to the StorePage in the Deactivate of each page (on both the inner and outer pageframes) and when the page containing the inner pageframe (PageA3) activates it automatically runs the Activate of the first page on the inner pageframe (PageB1) - something I wasn't aware that happens. This means of course that the Deactivate will also run for the inner page causing the StorePage to update the oPages array property with the wrong value (well, undesired value at least; perhaps not wrong, per se). What this means in execution is that whenever I click on and then off of PageA3 the reference stored is for PageB1. Any ideas? Thanks!

I'm not actually calling it from .activate or .deactivate, I'm calling StorePage from pageframe.activepage_assign (for the master pageframe, plugin pages are handled separately, i.e. manually) something like

thisform.storepage(this.pages[m.vnewvalue])

And there's also the part of the code you already got, which uses the full name of the page to check whether the page is already stored or not. You can tweak that code to suit your needs.
For some exceptional cases, I've also added an UnstorePage, which is called the same way as the StorePage, only it nullifies the reference to the page, removes the line from the oPages array and decreases the counter. That's for empty pages which need to be skipped - meaning "don't activate this page, it's blank in this scenario, unregister and jump to next - and don't visit it on the way back either".

Any code which would fire during the activate can be bracketed away somehow. I was also having trouble with some of it, but not as much, because the parent pages were blank, so there was practically nothing in the activate except the code to create the child page if need be.