>>>>Is Visual Source Safe the only source code control product that works with VFP. Has anybody experience with another products ?
>>>
>>>You can use the CVS (http://www.cvsnt.org/, at the server side) and Jalindi Igloo (http://www.jalindi.com/, at the client side) combo. It works really ok - and fully integrated - but please make a backup copy of your project before adding it to source control (I experienced some occasional problems with the initial import, but after that it works smoothly).
>>
>>
>>Your experience mirrors my experience with CVS.
>>
>>We went to CVS because PVCS gave us problems versioning the methods in forms, Also, you either had security which was too tight to be practical, or you had no security at all. Besides that, PVCS changed hands several times and account reps never kept up with our needs or situation because they were changing all the time. All in all, PVCS was a pain in the neck and we gave up using it.
>
>Hi Jerry!
>Two questions:
>1) What you use to manage versioning using CVS ?
cvsnt_1.11.1.3.exe contains what I used

>2) Are you also using Jalindi Igloo on client side ?
I began with WinCVS because you can also have cvsnt on the same box you are running VFP on. You have two modes of setup, depending on if you run on it your dev box or on a server.
Igloo is better, imo. Both work better if you use the modified SCCTEXT.PRG that was mentioned by another poster.
JLK