John,

>i see only 3 possibilities:
>
>1) Those recommending VSS for VFP do not use vcx'es.
>2) Those recommending VSS for VFP have not tried it themselves.
>3) I've gotten something all messed up.
>
>Whatever, VSS languishes in the drawer and the CD gets chewed by the baby.

We use VSS with VFP and use VCXes in many projects. We do it like this:

- VSS has a bunch of folders in it, all assembled in a hieerarchy the same way a developer would have (for example, a LIB folder at the top level that has VCX files we use in all projects, and then the project folders for each project).
- Set working directory on the developer machine to match the top level directory in VSS (in other words, make folder hierarchy the same on local machine as it is in VSS).
- within each project, attach to whatever files are needed, going wherever in the hierarchy is necessary. For example, a project in C:\VFP\PROJECT might attach to files in C:\VFP\PROJECT and C:\VFP\LIBS.
- any time you check out a file from a project, it will appear checked out to anyone else in that project or in a different project that links to the same file.

No, there is no way to have two people work on the same VCX, but then I am not sure I have ever heard of an SCM tool that allows simultaneous changes to binary files and allows them to re-merge. We break out VCXes into logical chunks, and on most of my projects, I have a separate VCX for every form (I user class-based forms). We do have some monolithic VCXes that cause us problems, but for the most part we are able to work OK as a team. We have 5 programmers and over a dozen large projects that are sharing all these areas...

Good luck!

JoeK