>>There aren't any advantages in creating everything programatically and
>there are many disadvantages in doing so. VFP was created to make use of
>visual tools. By avoiding these tools you are creating extra work for
>yourself and a headache to boot. If you really want to look at some code,
>you can always use the class browser and view the code from there. Note: I
>am talking about using VFP's visual tools, not VFP's wizards, which are
>good for quick down-and-dirty apps, but practically useless for any large app.
>>
>>The only time I can concieve of creating classes programatically are for
>things like creating dataenvironment classes or grid column classes, which
>can't be done visually.
>>
>
>I can see where the tools provide a much faster way of developing an app
>and I certainly wouldn't want to develop an entire app with hand-coding
>unless it was an incredibly small app. I guess my question is, if there is
>a tool to do the job, why do some people still hand-code stuff at all?
>Let's just limit the discussion to subclassing a control. Is the hand-coded
>version any more efficient? Do the tools add a lot of extraneous stuff that
>would slow things down?


I don't know of anyone that hand-codes unless, as I said, it is for something that VFP doesn't support, such as visually subclassing the dataenvironment or a grid column. The tools don't add any extraneous stuff. To see this, just look at the code from the class browser.