C5 Errors Using Vault with VFP9 SP1

[holzert]

Project exists in vault (added from the primary workstation). In the past, I successfully joined this Vault project from within VFP9. Since then, I received a new pc and installed the vault client.

On the new pc, I set the repository, chose the directory in vault, and set the working directory for the project.

I then clicked on 'Get Latest Version...'

Once the files were downloaded, I opened VFP9 and typed in the command window 'Modi Proje' Immediately a C5 was generated with no specifics. vfp9err.log shows only its own line, no specifics.

If I remove all source control information from the project table (sccdata field) I can modify the project fine.

If I click on add project to source control it produces a c5 error.

I have deleted the foxuser files just for gp to rule it out

Are there any dependencies I may be missing? Framework 2.0 is installed.

TIA,

Tracy

[lbauer]

We don't support integration with Visual FoxPro, but some Vault users have used it successfully.

It sounds like you're doing a get with the Vault Client and then opening the project with VFP. In Visual Studio, a project must be opened from source control to establish the proper bindings.

You may have to do the equivalent of that in VFP. This would mean backing up the project files from your working directory, then retrieving the files from Vault via VFP.

Some user experiences that might help:

http://support.sourcegear.com/viewtopic ... ght=foxpro

If any Visual FoxPro user have suggestions, please post here.

[holzert]

I uninstalled VFP9 completely, deleted all registry settings, deleted all directories and likewise with Vault.

I reinstalled VFP9 and VFP9 SP1.

I reinstalled Vault Client.

I setup VFP9 to use Vault as its Source Control.

I started VAult, selected the repository, set the working directory, and got latest version.

From VFP9 I attempted to modify the project and received a c5.
From VFP9 I attempted to create a new project and add it to source control and received a c5.
This occurs from within VFP6 as well.

All other workstations can do these tasks with no errors, and before I received my new workstation I COULD AS WELL.

I can, however, use Vault and Visual Studio 2005 together FINE with NO ERRORS.

It appears that something is broken between Vault and VFP9 but only on my NEW machine, since the identical steps above work on all other workstations.

Are there any dependicies for Vault ? I have net framework 2.0 installed, VFP9 and VFP9 SP1. Anything else?

I can run Vault alone or from Visual Studio but not from inside VFP - any call to VAult produces a c5 on this workstation.


TIA,
Tracy

[holzert]

Resolved.

Installed Net FrameWork 1.1 (and then reinstalled 2.0) and it works now. I had only Framework 2.0 on this new workstation (no 1.1 on the new workstation) which doesn't work I guess.