>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?

For my .02 US, I prefer to use the class designer - I like having each method title on the property sheet (I use 'Non-Default Properties Only' a lot). Also, I have many small libraries which can be moved from project to project easily.