Brian,

IMO, my suggestion to you would be to not allow more than one developer to check out the same file. VSS has merge capabilities for this situation but aren't, IMO very reliable.

The PJM file is something that VFP is doing, not VSS. You need to add a project to VSS from within VFP using the Project Manager for the PJM file to be created. The PJM file is an ASCII representation within VSS but each developer has an actual PJX/PJT file locally. In VFP menu, Project/Source Control/Update Project List... will update the PJM file with the developers changes and also update their local PJX with other developers changes that were updated to the PJM.

One Note: Whenever we Update Project List..., VFP Checks Out the PJM, updates it and Checks In the PJM but leaves the status as Checked Out so we have to manually, in VSS Explorer, Check In the PJM file again before another developer can choose Update Project List...

HTH

>Hi Craig,
>
>Sorry to bother you, but I am really a newbie when it comes to sourcesafe. Being that the .pjm is an ascii representation of the project files, what would occur if more than one user had say for instance a class inside the project checked out and both had made changes to the class in question? Would it show it like it does for program files and allow you to merge the changes? If not, then what does occur?
>
>Thanks,
>
>Brian