>Hi, everyone.
>
>I was trying yesterday to set a builder for one of my classes. I have added a .Builder property, then wrote in it the full path to my builder form. Suprise. MemberData Editor menu entry stopped working, because it calls my builder now, instead MemberData Editor form.
>
>By trial and error I have found that if I rename the property to .BuilderX, problem solves, however this raises several questions:
>
>#1. What's the difference between .Builder and .BuilderX?
>#2. Can I also use .BuilderY? or .Builder + any letter/group of letters?
>#3. Why MemberData Editor stops working if I add my own .Builder property? MemberData editor is defined in Builders.dbf anyway - it doesn't need my property in order to work. Why it is reading it?
>#4. If I store all my builders in an .APP file, what's the synthax that I need to enter in .BuilderX property in order for Builder.App to open my own app and call a specific form from it?
>
>Thank you

When I did some research on builders some months ago, it seems that the knowlegde of why there is a BuilderX is kind of lost. I could not find complete info on BuilderX, BuilderB or what Ken Levy did, on the Internet, all links in the end get you to dead pages.

It seems Ken Levy made some kind of app to create builders, "BuilderB", and the resulting builders where called by the BuilderX property.

I found now: BuilderX: This property is the visual class that points to the BuilderB Builder for this class.

http://fox.wikis.com/wc.dll?Wiki~BuilderB~VFP

This is how I create a builder:

BuilderX : =home() + "wizards\ctl32_progressbar_builder.app"

If you download the ctl32_statusbar class from downloads, inside you will find the builders I did, they are apps that copy themselves to home() + "wizards" when clicked on them. You dont have to deal with builders.dbf or anything.

In the builder app you get a control reference as a parameter when invoked, so you can do what you want based on that control class, etc.

Carlos