Do not totally disagree with you, but situation dicatates that by selecting a response, another set of responses are required. In this case, the tabs will not be available, only using the pageframes for collection of other controls and the proper page is activated based on a previous reponse.

Other reason we use this approach is that when a UI has multiple pages and the order of pages appear to toggle from row1 to row2 etc based on which tab is selected has become confusing to the user. We found by minimizing the tabs that the users perferred this approach that when a tab is selected, the pageframe on that page will always stay below the selected page that they began with.
Now the users do not want to deviate from this design and I am forced to use the standard pageframe on individual pages rather than our subclassed pageframe.



>You won't like my suggestion, but since you asked...
>
>Rework your UI. A pageframe on a pageframe is not good UI design. It tends to be difficult for the user to navigate.
>
>>In my base class, I have the pageframe subclassed from the standard class. On a form, I have a pageframe and on page1 I drop another pageframe onto it and in that page1 I drop another pageframe.
>>(thisform.pageframe1.page1.pageframe1.page1.pageframe1....)
>>
>>Everything works find. However, when I select these controls and save as a class and then drop the container on a form I get an error where class definition is cyclical.
>>
>>I can do the same with the standard pageframe which is not in a container and everything is okay.
>>
>>I have re-named each pageframe, page etc. and can not seem to figure out why the placing in a container causes the error.
>>
>>Any suggestions would greatly be appreciated