Hi!

It is a really messy problem in VFP. To update local project from pjm file on the server you can only join to that project again. When you use update project list option, it just overwrites someone's changes by the current state of the PJX/T files on the local machine. Just delete PJX/T files and join to project again to get latest project structure.

As about checking in PJM file - keep it one on the VSS. However, we use VSS native client application (VSS 6.0) to check in this file each time after Update Project List or after Joining to project.

HTH.



>Hi,
>
>I am having trouble understanding how VSS source control works within a VFP6 project.
>
>As I understand it, the VFP .pjx/t files sit on the local hard disk of each developers machine
>
>The .PJM file sits in VSS with a local copy on each machine
>
>When a developer has made changes, he hits "update project list", this copies all local changes back into the central PJM and gets other developers' changes
>
>Problem is that the PJM file is then checked out on the VSS database and other developers cannot run "update project list"
>
>Should I have multiple PJM's on VSS (1 for each developer)? or should I enable multiple checkouts? (Which I really don't want to do!)
>
>TIA
>
>Will