Joel,

The PJM should be the only file set to allow multiple checkouts. What kinds of conflicts are you running into? There really shouldn't be any at the file level. As each developer adds new files to the project they are only doing it to their local project (pjx/pjt) although the source file is added to VSS proper. The other developer should simply have to do an Update Project List to see the files added.

>We are having problems keeping our projects in sync among multiple developers. Part of the problem is having to merge the PJM file and figuring out how to handle conflicts. To prevent this problem, we want to disable multiple checkouts so that only one developer would check out the PJM file at a time. We can't get Update Project List to work in this scenario. Here is the process we are using along with the results:
>
>1) Developer 1 (Dev1) adds a file to the project.
>2) Dev1 checks out PJM file.
>3) Dev1 updates project list.
>4) Dev1 checks in PJM file.
>
>At this point, the PJM file shows the new file.
>
>5) Dev2 checks out PJM file.
>6) Dev2 updates project list.
>7) Dev2 checks in PJM file.
>
>The new file is NOT added to Dev2's project, and the new file is no longer listed in the PJM file under source control. It appears that VFP simply overwrites the PJM file with a representation of the current developer's project, without considering the changes made by other developers. Does anyone else see this?
>
>If I re-enable multiple checkouts and have both developers check out the PJM file, then the new file is added to the project as expected. Of course, this opens me back up to the merge/conflict problem. I have seen recommendations for disabling multiple checkouts, so I must be doing something wrong. Any suggestions?