>>>I read all the thread and at End I understand what you want.
>>>In Tools/Options/Forms you can activate Builder Lock and Create a Builder and Register it in VFP and allways you insert the class
>>>the Builder will Start
>>>
>>>I don't know how to do it but you can Investigate how to do.
>>>
>>>I hope this help
>>
>>Yes, Christof Lange told me about the builder lock. That, however, is a little too much. It forces ALL builders to be executed, but what I really want is some code to execute when this specific class is dropped on a form, not when ANY class is dropped on a form.
>>
>>Thanks for the suggestion!
>
>Fred,
>That's relatively easy to work around. Create one program that wraps all builder functionality. VMP uses this technique because it has several builders. The classes it doesn't have builders for it passes the parameters on to the VFP default builder. You could simply do this or just return.
>
>HTH.

Does this "master builder" get invoked only at the time builder lock is used, or do you mean to set it as the builder for all controls, using the builder property? I'm looking for something that doesn't require *any* intervention by the user to kick of this code (not necessarily a builder, but it will have some builder-like qualities to it). Vlad G. may have pointed me in a direction that can do what I'm looking for more completely.

Thanks!