Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Integration in Visual Foxpro
Message
General information
Forum:
Visual FoxPro
Category:
Source Safe Control
Miscellaneous
Thread ID:
00860140
Message ID:
00860414
Views:
12
Thanks a lot Frank, I suspected it was something related to the registry and it was.

Thanks to your 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,

Gil

>Hi, Gill
>
>
>
>>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.
>>
>
>I have been in this situation many times and it was driving me crazy till I found the answer at: (Replace SOS Collab with your sourcecontrol provider)
>http://www.sourcegear.com/soscollab/support/faq_ide.asp#foxpro
>
>=======================================================
>Visual FoxPro does not recognize SOS Collab as an active SCC Provider even though I made it my default SCC Provider during install. How do I fix this?
>
>The list of Source Code Control Providers is stored in the system registry under:
>
>HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders
>
>It appears that Visual FoxPro stores a cached copy of this particular registry key. For some reason, this cache is not updated when a new value is added to this key. An update has to be forced. We have found that renaming one of the value names in this registry key forces an update of the cache.
>
>The following steps should correct this problem:
>
>1. Exit Visual FoxPro.
>2. Launch the Registry Editor (regedit.exe).
>3. Go to HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders.
>4. Under this key, right-click one of the value names that existed before SOS Collab was installed and select "rename". Add a "B" to the end of the name and save it.
>5. Now, right-click the value name again and select "rename". Remove the "B" from the value name and save it. So, the value name should now be as it was initially.
>6. Exit the Registry.
>
>Next time you launch Visual FoxPro, SOS Collab should be listed as an active SCC provider. Choose SOS Collab from the drop-down box and click "Set As Default" to make SOS Collab your default SCC Provider.
>=======================================================
>
>
>>TIA
>>
>>Gil Velasquez
>
>hth,
For every bug fixed, there is a bigger bug not yet discovered.
Previous
Reply
Map
View

Click here to load this message in the networking platform