>Fred and Joe,
>
>Installed VSS 6.0 client on my machine overwriting the VSS 5.0 client. This made (obviously) VSS 6.0 the default.
>
>My 6.0 VSS database is called VSSWebSrc located on server B (No VFP projects)
>My 5.0 VSS database is called VSSSrc located on server A (All VFP projects)
>
>Problem: When I go into VFP and Modi Proj xx (or any of the other 5 projects contained in the VSS 5.0 database) which originally pointed to VSSSrc, the project gives me the SCC API error "Project Created" occurred. The project will be opened without source control. Behind the scenes VFP tried to look for the xx proj in the VSSWEBSrc (6.0) database (not the 5.0) and added an empty VSS project xx to VSSWEBSrc.
>
>I thought that I was going to be given a prompt to select the database to work with after loading the VSS 6.0 client and then I could pick the VSS 5.0 database.
>
>Need: Without converting the VSS 5.0 database to 6.0, how do I reset the default for each of the VFP projects contained in the VSS 5.0 database to look there or worst case prompt each time the project is opened?
>
>Thanks in advance
>
>Dave

I'm not real sure you can quite get there from here. What you can do is go into your VSS database under administration (from the Start/Program Files/Visual Studio/Source Safe/Admin menu names are different than these, but you should get the idea) and change the default database.


>
>>>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
>>>
>>
>>When you install VSS 6 and it finds an existing VSS 5 database, you're given the option to convert it to 6.0 format or not. If you keep it in 5.0 format, you can access it with either a VSS 6 or a VSS 5 client. You can't have both clients on the same machine (at least I don't think so).