>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. ?
>

It actually is an ASCII representation of the PJX/PJT, in much the same way that the VCA is a text representation of the VCX/VCT, etc.

>2). It checks this file out in VSS.
>

Yep - this is what is checked in/out rather than the PJX itself.

>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.
>

In the same way that you don't see the VCA, SCA, etc. It's a metafile managed by SCCTEXT.PRG during VFP checkin/checkout.

>4). To check in this file you have to goto VFP.
>

Yep - It's written every time the Project List is updated.

>5). Do you ever check in this file.
>

Only indirectly. Again, it's the same issue with VCX/SCX/FRX - the ??X/??T never make it into VSS, only the ??A (or in this case, PJM) are moved in and out. If you need to manually check things in and out, you need to have VFP running so that SCCTEXT can do its thing and build the needed binary files from the text representation.

>6). Please state anything you else regarding this area.
>
>
>I would buy a book but there does not appear to be any.

There are references scattered about in the VFP docs; as usual, Hacker's Guide has some useful insights. It boils down to if you use the SCC integration with VFP and VSS, you need to work from VFP because of the issues of how things are saved from files that are part of the source code but aren't truly text files.