I was able to do the same, but then again if I kept up the process, the second addition of this new pageframe had the same issue. However, I can use the standard pageframe with no problems. It seems that by subclassing the pageframe there becomes a problem.



>Ronald,
>
>I have seen this before. I got around this by creating a second pageframe class and dropping that class on a page.
>
>
>>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