Dave,

>Not that I'm afraid to take MSFT's word right out of the manual, but......

Now why would you be afraid to do that? *smile*

>Our workstation projects have remained in a VSS 5.0 database located on a NT server and have been stable. We have added a new server specifically dedicated to our WEB framework and projects that I have set up VSS 6.0 on.

Sounds like exactly what we did about a month ago...

>Problem: developers will obviously be working in both VSS worlds and I am concerned about loading/running NetSetup.exe for 6.0 on a client machine that already has 5.0 loaded for fear that pointers, etc. will get confused and I'll be in for a very long weekend trying to sort out the pieces..... the VFP/VSS 5.0 integration has been very good (once all the "Nuances" were discovered and processes employed around them) but if I load the VSS client 6.0, will VFP recognize the difference from within each project? What other impacts?

I had some developers overwrite the 5.0 client and some install in a new spot, and everything seemed to work. The only thing you need to do after getting the new client installed (I recommend just installing it over the 5.0 client) is to make sure your database list looks OK. I assume you will have folks pointing to both the 5.0 database and the 6.0 database? I just made sure all the developers had their database lists set up correctly, and then I started migrating projects from 5.0 to 6.0 by getting the latest from the 5.0 database, detaching from 5.0, and then placing the project under the 6.0 database.

Remember that VFP itself is not good at switching between databases. You have to fire up VSS Explorer, switch databases, and when you do so make sure that the "Use this database the next time I open VSS" is checked so that when VFP fires up the VSS engine under the hood, it goes to the right spot.

Your best bet is to not have the same project in both database at once (we had to becuase of extenuating circumstances) so that if the developer is pointing to the wrong spot, he or she simply doesn't find anything. Once people get familiar with switching between databases, you should be fine! I thought it was going to be a nightmare of crossed wires, but I was pleasantly surprised that we all got it working with relative ease.

Let me know if you have any other specific questions I can address. It can be a scary bullet to bite, but for us it helped a lot because we started with a fresh version in 6.0 and it seems to have helped a bit with project update times, etc. since there aren't so many deltas to wade through (many of our files had 200 or 300 versions to them)...

Good luck!

JoeK