>>>Should each developer keep a separate copy of the project in his machine or perhaps in a special directory? I ask because VFP keeps complaining about the project being in use.
>>
>>Yes, you actually keep a separate local copy on each machine of the project and the source code. SourceSafe merely acts as a central database of the "latest working" versions.
>
>Thanks Fred. Could you explain the whole process a little more, please. Imagine I knew nothing, which is not very far from the truth.
>
>Thank you very much.
>
>Alex

OK, I'd suggest you start with a new SourceSafe database. You do have 6.0c, don't you?

Once you have a new empty database, you need to make sure you have Microsoft Visual SourceSafe turnred on as the Active source control provider under Tools/Options.../Projects. Once you have done that, you should then have additional options under your File menu (Join Source Control Project...) and under the Project menu when you have a VFP project open (Add Project to Source Control...).

Open your project and do the Add Project to Source Control from the Project menu. This will add all your files in the project to SourceSafe. Once the project is under source safe control, you'll need to enable multiple checkouts (in VSS). Then your other developers can "check out" the project by using the File/Join Source Control Project.

I may be a bit light on the details as I haven't set up a new project in awhile. I'd also suggest you get Ted Roche's book Essential SourceSafe from www.hentzenwerke.com. Lot's more details there, too. There's also quite a few MSDN articles you can search for online on "how to" setup SourceSafe.

Hope that gives you a better start!