Kevin,

now I understand ...

I'll have a look at the places you pointed me to in a few days. I've just read Doug Hennig's "Builder Builder" article in FoxTalk and that made me want more < g >. So I had the idea of integrating some kind of a "Builder Builder" into my project, but since I'm still very busy, I'll have to wait for the fun with Builder Builders a while ...

Thanks,
Armin

>As you've already seen, the Builder property contains the name of the class. Although this may seem redundant, it allows the builder classes to determine the Framework class from which your custom controls are derived. For example, if you create two layers of subclasses:
>
>CTextBox -> ATextBox -> MyTextbox
>
>how does the builder class know when your right-click on MyTextBox which builder controls to use? It looks at the Builder property and, knows the class derives from the Framework's CTextBox class. From this, it determines which builder classes use. Check out the GetControlClass() method of the MMBuilder class (found in MMBuilder.vcx). You'll see that the value stored in the Builder property is used as a lookup key into the Framework's MMSecCtl table. This table contains the name of the user interface class (e.g CTextBox) and the name of the associated builder controls class to instantiate...it's actually an abstract factory!