>When you create a new project in VFP and then add that project to VSS a new project folder is created in VSS.
>
>The new project folder contains a link to a file project.pjm not the VFP project files.
>
>Please note any observations you may have on the following
>
>1). I suspect the PJM file is a controlling point for the project and VSS uses this file to control both of the VFP project files. Is this .T. ?

PJM stands for ProJect Metafile. What you've stated is basically true, I'll elaborate below.

>
>2). It checks this file out in VSS.
>
>3). From VFP, when you check in files you do not see this file as a possible check in point. So you cannot check in the project itself.

Correct. You don't check in the project, you Update Project List.... This is under Project/Source Control menu
>
>4). To check in this file you have to goto VFP.

Actually, I've found VFP leaves this file checked out when updating and I need to chech in using VSS Explorer
>
>5). Do you ever check in this file.

Yes. See 3 and 4

>
>6). Please state anything you else regarding this area.

The basic of the PJM file can best be explained in a multi developer situation:

You (D1) and another developer (D2) are working on the same project. Both D1 and D2 have their own project files locally. If D1 creates a new form called myform1 in the project and adds it to source control D2 will not see it. This is because the PJM file in VSS has not been updated to show this new form. When D1 chooses Update Project List.... and then D2 does the same after then D2 will see myform1 in their local project file.

HTH

>
>
>I would buy a book but there does not appear to be any.