Hmm.. I was hoping you could expand a bit... I have used VSS as a single user and have loved it. When we have tried to implement it in a multi-user we have problems with the PJM file.

It seems that whenever I have a project open, other programmers can't open it or the PJM file is marked as checked out. When I add files to the Project and choose the Update VSS Option from the Project Menu it doesnt update it. Other users are having a bear of a time keeping in sync...

It seems that you are using it successfully so I was hoping you might be able to shed some light...

Thanx!
Bob :-)

>>We have a problem with the way visual sourcesafe handles projects. I add a
>>file to the project it doesn't automatically puts in in the PJM file, I need to
>>do a update project list for that.
>
>Right. Every programmer has their own copy of the project and PJM. You need to update the project list to let everyone else know you're ready for it to be part of the project.
>
>>If we add a file to the project the other programmers don't get an automatic
>>dowload of the file. They need to either pull it with VSS itself or by having
>>the PJM checked out all the time and resolving conflicts when they do update
>>project list. How do we solve this issue ?
>
>You should never need to go directly into VSS while working on a project, unless you're doing something like labeling the current version. Everything can be done from the project manager. Once a programmer gets the PJM checked out, it stays that way, and Update Project List synchronizes the local copy with the version on the server. Conflict resolution with the PJM works just like conflict resolution with a PRG: if someone else has changed something, and you've changed it in a different way, you need to tell VSS how to deal with it....
>
>>How does the .PJM deal work
>>exactly ? Where can we find more info on this.
>
>The VFP5 Online Documentation goes into quite a bit of detail about Source Control: try there for starters.