4.1.0 Client works with VFP IDE, 4.1.3 Client does not

[HankFay]

Yeah, I know that VFP isn't supported and that you don't have a copy (although if you have MSDN Universal Subscription, and if you have any MVP's like Martin Woodward working there, you do have a copy of the Universal MDSN). That said, we've been using SOS and then Vault forever (well, SourceGear's forever, anyway...).

Having used Vault 3.5.3 since it was released, I was looking to putting 4.1.3 (latest and greatest) on a new server, database replication, the whole ball of wax. And when I went to Add Project to Source Control, it would get past the Select Repository dialog, and then nothing. The Project did not get added.

In communicating with Tracy Holzer on the Universal Thread, I learned that her team has been using 4.1.0 since March 4, 2008, without any problem. So... I uninstalled the 4.1.3 client, installed the 4.1.0 client, and what do you know: it works! Not only that, the "error" dialogs that would appear on project startup and on certain operations are fixed. That is a beautiful thing.

So something apparently got "fixed" in the 4.1.3 client ...

Other results:

On 4.1.2, it is partially broken: when attempting to add files to source control, it hangs. I guess 4.1.3 fixed that problem.

4.1.1 gives the same results as 4.1.2. So that's when things broke. This was, according to the release notes, also the version that first fully implemented the Vault Client API. That, I believe, resembles a smoking gun.

Any chance of finding out what broke between 4.1.0 and 4.1.1 and fixing it in 4.1.<n>?

thanks,

Hank Fay

[jeremy_sg]

I expect that the bug is actually the same one that is affecting our Visual Studio 2003 integration. We have a prerelease 4.1.4, if you want to see if that fixes your problem. Please email support at sourcegear.com ATTN: jeremy with a link to this thread if you want to try it.

[jeremy_sg]

Hank reported that the 4.1.4 prerelease did work for VFP.

hs: 214083