>I don't know why having a unique name for every contained object is such a hassle for you guys. I don't know of any OO language that supports a rich containership model like VFP that doesn't require unique names. Contained objects aren't really different than a property, would you argue that properties don't need to be uniquely named?

"Such a hassle" - well, it is just that having a simple array of objects seems a little simpler to me, than using macro expansion to create and access the objects.

>You can use the Objects[] or Controls[] collections to iterate through the contained objects without regard to their names.

I know this - but sometimes I want to loop through a very specific collection of objects - not all objects on the form. Well, I guess I could create an invisible container for the specified objects. As a matter of fact, I think I will include this as a fourth alternative.

>Using a secondary array or cursor to maintain your own collections is really needless extra work.

Why "secondary"? I use the array instead of the individual object names - not in addition to them.

Hilmar.