That's exactly right Fred, rather than having both entries show up on the source control provider listbox, there was only one, the PBNative one.

Since PB is not used here anymore we decided that it wouldn't hurt trying to delete one to see what happened. After we did it, it worked fine and now we can continue working.

The reference I mentioned is at http://www.sourcegear.com/soscollab/support/faq_ide.asp#foxpro

Thanks!

Gil


>>Hi Fred, thanks for your response; a fellow threader pointed me to an article where it shows a section on the registry where this is controlled and after deleting an unneeded entry I was able to make it work.
>>
>>Based on this reference, I was able to go the section in the registry where source control is specified and noticed there were two sources; one for Power Builder (PBNative) and VSS. I simply deleted the PBNative entry and presto!.
>>
>>Thanks again,
>>
>>
>
>Maybe I'm not quite understanding what you're saying here. You had two entries in the registry, but the PBNative one was causing the VSS one not to show, or was it causing no entries at all to show in the drop down list? We used to have another Source Control package installed at the same time as VSS, and they both used to show as available in the VFP drop down list. Never tried using the other package with VFP and I don't even remember what it was.
>
>Either way, glad you got it sorted out.
>
>
>>>>We have VSS from VS 6 installed and after installing VFP 7, cannot see VSS as an item under the active source control provider dropdown.
>>>>
>>>>Is there a way to fix this? We need to tie in source safe so we can get the current source code for our project.
>>>>
>>>>TIA
>>>>
>>>>Gil Velasquez
>>>
>>>VFP5 used to include SS.REG to register it. I don't find that file with any later versions of VFP, so maybe you need to re-install VSS?