Thanks Hilmar. I forgot to mention that the software is allready delivered and we mainly do maintenance stuff. The way they work now is that every developper have their own project, but all source files are on the server. The server is their "repository".

They control versioning with folders. They have one folder for each version they have installed at the client site. It works, but it's error-prone because it's easy to miss a file or to corrupt an old version.

They don't have any problems now if two or more developpers are working on the same VCX, given that they do not work on the same class. With source control, you can't check out only one class inside the VCX, you have to check out the whole VCX and no one can update any other class inside it while you are working with it. That's their main concern. I have given up VCX for classes other than GUI (I use PRG classes) for this reason and because it's easier to do a file diff, but they allready have a lot of VCX classes and most of them are GUI related (mainly all their forms are VCX based).

Of course, I can't ask them to rewrite their VCX classes in SCX forms and PRG classes just to integrate VSS (or to rewrite all this stuff in C# to get over this VSS integration problem.) I fear that I won't be able to convince them to go with VSS for VFP, unless I find a real good reason on why we absolutly must use VSS.

>For a team of more than one programmer, having some source control program is almost a must. I mean, of course you can combine the different files from different programmers, but without some software to do it, this would be quite clumsy and error-prone. You would need to designate one person in charge of having the "repository". Having this automated through software saves you a lot of time.
>
>Even for a single programmer, source control is very beneficial, since you can easily look at some previous version of a form, class, etc.
>
>As to the problem of taking out a single class from a class library; well, you will have this problem with or without source control software. It is sometimes suggested to have only a few (or even one) class in every class library; I find this clumsy. Perhaps you should designate one main person in charge of a class library, and use "manual source control" if required.