Join Source Control Project from Foxpro 9

[sethwilpan]

It may be ignorance on my part, but I'm having trouble setting up Vault to work with Foxpro 9.

I've tried creating folders in Vault, adding the Foxpro project files, but when I try to Join a Source Control Project from within Foxpro, the project files are not visibie.

I've tried adding files to source control from within Foxpro, but each time I select the SourceVault folder the folder selection dialogue just keeps reappearing in an endless loop.

Can someone point me to the steps to take to put an existing Foxpro project under Source Vault?

Thanks.

[lbauer]

Vault doesn't officially support integration with FoxPro, but perhaps some of our users have had success with it and can respond.

Otherwise, we'd suggest using the standalone Vault Client for scc operations and FoxPro for development.

http://support.sourcegear.com/viewtopic.php?t=195

[HankFay]

You have to Add a Project to source control, not Join a source control project. This is from the Project menu. The Join is from the File menu. Once a project is added, you can Join from another computer (this is in fact how you put the same project on multiple computers).

[HankFay]

I just checked and Vault works fine with VFP9. The usual (for non-VSS) rules apply. You get the fake SCC error which you ignore. You have to create the "projects" manually before you add the project to source control. Other than that, it works fine, and in fact, is fast. I haven't tried remote access to test that speed; probably get to it sometime this week. As it looks now, we'll be planning to switch over from VSS/SOS to Vault, if the remote tests hold up. And I do like the availability of an API to work against.

Either I've learned more, which seems unlikely, or the product has improved since versions 2 and 1, both of which I tried out and which left me unimpressed. I'm glad your question provoked my curiosity.

[M2r4Miller]

I just installed the Vault server 3.1.8 and successfully connected my VFP 9.0 projects to it.

After the installation of the server, I found I had to create a project in Vault with the same name as the VFP project.

Then in VFP, I set Vault as my default source code provider (tools-options-projects).

Once that was done, I simply opened the project in the VFP Project Manager, and selected "Add to Source Control", logged into Vault, selected my Repository and then made sure the project name displayed in the "add" dialog matched the name of the Vault project I created earlier.

After all the files are added, when I check out a form to edit it, both the .scx and .sct are checked together, and both are checked in together when that time comes.

Anyway, at this point, Vault is working perfectly with my VFP 9.0 projects.

[Darwood]

You get the fake SCC error which you ignore

Is the fake SCC error the one that says SCC API error "unrecognized warning" occurred? I get this problem using SOS. My post regarding this is at http://support.sourcegear.com/viewtopic.php?t=8805

Any idea what the cause of the fake SCC error message is? It's really annoying.