>I've recently joined a company that works with both Foxpro 2.6 for Windows and Visual Foxpro 6.0. The company has inherited a system with 4 projects in FPW2.6 and 4 projects in VFP6. The projects contain a large number of components and there are a large number of components shared amongst the projects. We currently have no version control which as you can imagine is very unprofessional and bound to cause a problem sooner or later.
>
>I was wondering if anyone knows if Visual SourceSafe is a viable option for both FPW2.6 & VFP6 and if so how does it handle the fact that 2 different projects might be worked on at the same time and have shared components ?
>
>Thanks...
There isn't any reason that I'm aware of that would keep VSS from working find with FPW2.6, although it will not be as seamless as it is with VFP6.0. VSS also supports sharing components between projects nicely. Should be covered in the online help, but in a nutshell you add the files to one project, go to your second, choose "Share..." under the "Sourcesafe" menu option, then go back to the first project's folder to link the components you want.
Cheers - Dan
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
