Armin,

>Just wanted to get around the different coding for each container class which has a collection that holds references to it's contained objects. Just wanted to replace all the IF .BaseClass == "Pageframe" then use Pages, IF .BaseClass == "Grid" use Columns, etc.

The Controls[], Pages[], Columns[], etc collections were just the original design released in VFP3. They made the most sense at the time. After people started working with the tool we found there are a lot of situations where generic iterators would make for better code.

The Objects[] collection was added specifically so that we could use container type independent iterator loops. There are in fact the same as their named counterpart. The original ones still exist to prevent breaking old code, and in some cases it may still be clearer to use them instead of Objects[].

>I'm using Objects now and didn't experience anything bad so far. Do you think there is any disadvantage using the Objects collection for this? When I wrote the original message I was wondering, if there might be other differences to the "original" collections, since the order in which the references are stored are not the same. That made me think, that Objects was designed for a different purpose than the other collections and it's not execatly the same internally.