Michelle,

>Well, I considered it cheating because I added it to the main subclass. I should probably have subclassed the subclass.

The level where you add it is just a design issue. You add it high enough up the tree where it makes sense to do it. It also doesn't make sense to create too many subclasses because your behaviors fragment too much and it becomes hard if you end up wanting the same behavior in two subtrees that have developed. On the other hand you don't want to create "huge bushpig" (Steve Black's phrase) classes either. Sometimes it's good to use a design pattern to get around some of the design limitations of inheritance.

>That pages[] is handy. Does it still work if I add custom pages? If I can ever get this dang thing to let me do it...

Yes, container classes like PageFrame, Form, Grid, etc. all have collection arrays Pages, Controls and Columns that can be used to iterate through the contained objects. PageFrames can only contain objects derived from the Page class. Increasing PageCount causes instances of Page to be added. To get your custom cPage subclass you have to AddObject() it yourself.