Joe,

To beat this horse for the last time.... from your responses I am reading that you suggest replacing the 5.0 client with the 6.0 client on the developer machines. What I also think you are eluding to since I have said that I cannot upgrade my 5.0 databases to 6.0 is that I can use the 6.0 client ot work with the 5.0 database.... is this what your are in fact saying? I cannot find any documentation supporting that fact (perhaps no surprise there...) other than the following text within the VSS help itself which doesn't seem to agree.

{
Using VSS 4.0a and 5.0 with VSS 6.0
See Also

VSS 6.0 has a new database format. If you upgrade to this new format, VSS 4.0a, VSS 5.0, Macintosh, and UNIX 4.0/5.0 users will not be able to access the database until they upgrade.

The new database format must be enabled for faster database performance and label promotion.
}

Is this in fact what you are are suggesting and if so, I assume that this has been successful in your environment.

Dave



>Dave,
>
>>Thanks for the info.... it was very helpful (maybe I should give you a UT Point *smile*) You have made me feel more comfortable (maybe too strong a word regarding MSFT upgrades..<g>) with the idea of co-existence...
>
>No problem...yes, the stress level was high when we took the plunge...comfort was never state of mind. *grin*
>
>>I am really not looking to move the 5.0 projects into the 6.0 database because they are stable and I thought why immediately "fatten" up the 6.0 database. Therefore I'll be ADDING the VSS 6.0 client to each workstation that already has VSS 5.0 and the same project will not exist in two databases. I assume that I'll get the opportunity to point to a new folder location during the install.
>
>By installing from the Netsetup of the 6.0 installation, I believe it will automatically add the VSS 6.0 database to the overall database list for the 6.0 client.
>
>>Questions:
>>1. Will 6.0 become the default for the machine? (Some of our developers will not be spending much time in the Web world)
>
>6.0 will become the default, that is why there is really no reason to keep the 5.0 client around. The 6.0 client can see 5.0 and 6.0 database just fine, and I am not sure what will happen if you have 5.0 and 6.0 clients open trying to use different databases at the same time. I am sure the clients will be fine, but VFP might get confused. Which leads to:
>
>>2. If both VSS clients exist on one PC and I open an existing VFP project under 5.0 version control, when we right click on a file and "check out" please tell me that it will know which VSS version & database to use....
>>3. Same question as 2. but regarding a project under VSS 6.0
>
>VFP will use the last open database. Now, I am not sure what it will do if you have 5.0 and 6.0 both open but to different databases. Use the one that was selected latest maybe? That is why I recommend using the 6.0 client solely. I guess you don't have to overwrite the 5.0 client, but by just using 6.0 you will have a better idea of what database you are on, etc. The 6.0 client looks just like 5.0, so your non-Web folks should still be comfortable with it. Oops, there is that word again... *smile* With all of this, you can install it just on your machine first and see what you think of it, and then once you feel OK about it, implement the same procedure sfor everyone else...
>
>>Any other comments and/or suggestions on my approach are welcome....
>
>Otherwise it sounds as if you are using the proper modicum of cautiousness, and your plan sounds good! You have a great weekend too!
>
>JoeK