In a team environment, if you need to do some modifications in one class, you need to check-out the entire class library (VCX) for yourself. That mean that some other developper who need to make some changes in another classe in that same VCX is blocked until you check-in your version of the VCX.

You could do one class/VCX to bypass this problem, but this will clutter up your project manager window.

Another approach that I have taken is to forgot VCX and build your classes in PRG files. You still have to manage multi-user conflict if you build more than one class per PRG, but it is easier to split a PRG and merge it later than trying to do the same with a VCX. The big inconvenient is that the class browser doesn't recognize PRG classes (this will be fixed in VFP 9).

HTH

>When working in a multi-developer environment with source control is it a good idea to have one concrete class per class lib. ( Think Meer Mortals where there are no SCXs all forms are in VCXs ) The Framework/Abstract classes are expected to continue to contain 1..N classes
>
>My gut says that there would be problems with this, but I cannot think of anything significant.
>
>Why it is being considered is that there should be much less conflict between developers needing to make changes to different classes in the same library. In a sense all that is being done is repeating the organizational ( or lack there of <s> ) structure of a project that uses SCX forms.