Hi Alex.

Source Safe intergration with VFP required that all files be in the directory with the Project file, or some subdirectory under that. If you have a library of code that you share between other projects what I've found easiest is to do is -
1) Make a project in the shared code directory and add everything into it.
2) Put that project under source control.
3) Go into Source Safe and share the files from the Shared project into any project that needs the files.

This will give you a local copy of the files in each system that uses them, but when you change any of them the changes will automatically propogate to all systems that use them.

Ian Simcock.



>The saga continues.
>
>We have a project that needs to be added to Visual SourceSafe. The components of that project span multiple folders/drives (e.g., one PRG might be in s:\devdApps\SomeFolder\b.prg, another in c:\common\prgs\proc.prg, etc.).
>
>It seems that this sort of structure gives Visual SourceSafe problems? It keeps producing messages like FILE C:\_TMP\FFSOTHER\PROGRAMS\B.PRG COULD NOT BE MAPPED TO THE SOURCESAFE PROJECT $/FFSTEST for those files that our "outside" of the main folder structure (i.e., the folder structure that has the Visual FoxPro PJX at the top).
>
>I can think of a couple of work-arounds, but they are less-than-optimal (having to do with either sub(VSS)projects within the main VSS project, or just separate projects for each "root" folder than contains components that are part of the main Visual FoxPro project). In some brief testing of at least the first of these work-arounds there are still issues with VSS not being able to map to physical locations when doing any file in/out operations.
>
>Can anyone shed some light on this? In order for VFP and VSS to play nicely must all the components of a VFP project be within subfolders of the main project (VFP) folder? If so, how do you deal with files that are shared by multiple VFP projects where other projects are outside of that folder structure?
>
>Thanks!