Hi Alex.

There is no need to check the PJX & PJT in since VFP updates the project from the PJM as required. To cover your two points specifically,

1) If the project gets corrupted the easiest thing to do is delete it and rejoin the project (File / Join Source Control Project...) which will build you a new one. If memory serves you will need to first go into SourceSafe and UnDo Checkout on the PJM file first.

2) When you update the project list (Project / Source Control / Update Project List...) VFP merges the changes you have made ( adding or removing files) with the version of the PJM in Source Safe, rebuilds your project file from the merged PJM and then pulls copies of any new files that you don't have back into your development directory.

Ian Simcock.



>So a question concerning the PJX/PJT files. Do most sites that use Visual SourceSafe check these files in as well? From what I understand Visual SourceSafe will create and manage a PJM, which as far as I know is a flattened Visual FoxPro project file. However, is there a need/value/reason to manually check in the PJX and PJTs? I'm thinking perhaps for the following reasons.
>
>1.) In order to have a backup of the Visual FoxPro project in the event of project file corruption.
>
>2.) As a way of "checking in" new project components that one might add (or remove) from a project.
>
>Any thoughts?
>
>Thanks!