If it is for the cost, there is also free software in this same category - mainly CVS or something, I think. However, I have no idea how to make it work.

Of course, purchasing the software is not the only cost; it will take a while to get accustomed to a new way of doing things.

I think it is absolutely worth-while, but you have to see to believe. It is hard to explain. It is clear that I don't need to convince you - but I don't know with what arguments to convince others. Perhaps you can find some good article. For example, IIRC, there was one in an older edition of FoxPro Adviser.

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