>>Not sure I got the essence of your posting, but are aware that you can have multiple procedure files open at the same time, allowing you to put each "area of concern" in a separate file?
>>
>Hi Marc,
>
>Sorry I wasn't clear enough, let me try again. I design all of my classes using the class design tool in Fox. Everything is built visually. To include a custom class with a form, I just drag the class from the project manager and drop it on the form.
>
>My boss on the other hand, creates all of his custom classes in a prg using DEFINE CLASS. He includes these class definitions in his projects by adding a SET PROCEDURE to [prg] in his app. When he requires a custom class on a form, he does a CREATEOBJECT() in the INIT of the form.
>
>I prefer the visual route, he prefers to define his classes manually. My question is, what are the pro's and con's either approach?

it may very well be an age thing -- I prefer your method. Mostly because it saves some typing and I prefer having the non-visual object on the form -- easier to remember and find if something in it isn't working right...