>Hi Robert,
>
>AFAIK, control arrays are the mechanism used in VB
>for adding new controls at run time, with some predefined
>event code associated (the code the elements of the array
>share). This is not an issue in VFP, but u may need to
>change your design and replace control arrays with
>inheritance and object creation. Anyway if u really need
>it, you can have an array that holds references to objects,
>but by code.
>Hope this make some sense to you.
>
>J. Luis

Yeah, it does, except that I am after control arrays for different
reasons. I know where they are used (in all more or less sophisticated
OOP programming tools). VB (MS) just made it easy for developers
to create them at design time (you cannot create control arrays
at run time in VB, BTW :)

I need to change my design ? :) OK, I will :) But I don't want
to make it worse than it should be :) It is already full of
custom objects that I brought from my Visual dBase programming
experience (the only reason I switched to VFP lies in its
inherited superiority of DBE that WAS NOT developed by MS!)
Inheritance? But of course :) It's there!!! What I am after is
a true implementation of polymorphism, not 125 functions that
have the same code, i.e. This.Value = This.Parent.Caption, for
example. And if you need to change it from .Caption to .Tag, you'll
have to make this change in 125 places??? Not me :) In Visual dBase
I was able to implement polymorphism directly, because it is a fully
supported and enforced feature. In VFP - the only alternative I found
so far is to create control arrays and share the same code among them.
Do you know any other way? I would be glad to debate on a more efficient
way of implementing polymor...whatever that word is :) And believe me, -
once you try this concept, you'd never go back.

Hope I didn't make anybody upset with my comments :) If I did, then
hope my smiling faces smoothed the rage :)