David

>And of course, Mike, you can merge PRGs in source control!
>

I am not in favor of merging anything. Keep all code as atomic as possible. No two developers ever have to work on the same piece. Ergo, no merging required.

>>Whichever way you go, keep the number of classes in each prg or vcx down to one. See http://fox.wikis.com/wc.dll?Wiki~PRGvsVCX~VFP and http://fox.wikis.com/wc.dll?Wiki~VFPSetProcedure~VFP
>>
>>>Hi All,
>>>
>>>I and a friend are having a discussion on how to best create and maintain classes. He suggested that we programmatically code our classes. I, however, am very comfortable designing/coding classes visually - that is, using the Visual Class Designer.
>>>
>>>Although one can very well convert a VCX based class (or a Form even) to a PRG class via Class Browser/View Code, the issue of performance and best practices comes to mind.
>>>
>>>Which executes faster? Is coding classes programatically more popular? Or better practice?
>>>
>>>Many thanks to anyone who shares his/her insights!
>>>
>>>Dennis