>Hi Charlie ----
>
>>I like polymorphistic names, so I think MS erred by naming things like PageCount, FormCount, ButtonCount. It's a PageFrame! It has a count! The property should be Count. If something has a Name, I call it Name, not CustName. It's in the Customer table, so that's the context.
>
>I personally agree with the customer table argument, but several server database design tools would disagree.
>
>OTOH, it's PageCount, FormCount, etc. because it's a reference to a collection of the root object, NOT the root object itself. Therefore, PageFrame.Count would be non-sensical. Is this a count of PageFrames? Is this the Count number for this PageFrame? And what about objects that hold multiple collections...they can't all be Count, can they?

Since there are no other things you can have in the PageFrame except Pages, no other thing in a grid but columns... why not just ControlCount? Imagine how shorter would all the recursive routines which, drill into containers, be. No need to test the baseclass of an object to know what property holds its ControlCount. "Is it Tuesday? Then this must be Jakarta" (I think it was Kissinger).