>It looks like that the pjm file on the VSS side is reset to whoever updated it last. For example, I (programmer a) create a VFP project (project a) and add it to VSS. Another programmer (b) joins the project in his local directory. Programmer b adds a form to the project in the local directory, adds it to VSS, and does the "update Project List" function. Viewing the VSS pjm file finds the new form listed in it. Programmer b does a Update Project List. The project does not contain the added form and when the VSS pjm file is viewed it contains b's pjm file. The new form added by a is not there.
>
>I have tried this with and without multiple checkout and it doesn't seem to matter.

This is why I recommended doing a Get Latest Version every time the programmer starts working in the project, and an Update Project List whne they finish their session; if the Project was updated by someone else with resulting additions or deletions to the project, the local copy may be getting updated without the PJM being pulled down and merged first. Multiple checkout makes this worse.

I suspect that the .SCA for the new form is present in VSS, but that the PJM is out-of-sync. The SCX/SCT isn't checked in; the SCA serves as a metadescription pof the Form, which is used to rebuild the Form components on checkout.