Clarification of behavior

[eboykin]

Vault: v3.1.8

My company has recently switched from Source Safe to the Vault and while we are mostly happy with teh Vault we do have some issues. Most of these seem to stem from differences in how the Vault performs certain actions vs how Source Safe did them. This is not a criticism but instead just a question so I can give my folks a clear answer on what raelly is happening.

Ok, in Source Safe when you get latest, any files with differences are overwritten with what it in VSS (It doens't merge them by default).

In the Vault, get latest will attempt to merge different versions (by default). However, when ofcing the overwirte in the vault it will also overwrite Checked Out files?!? This is VERY different from VSS and has bitten more than one of our developers.

I guess in a nutshell, we were expecting Get Latest to always overwrite NON-checked-out files that were different and not to merge them and we were NOT expecting Get Latest with teh option ot overwrite to also overwrite CHECK-OUT files. Can I get an explaination of why this is the default and what the thought is behind it so I can better understand how/when to use this.

[Beth]

You may wish to check out this KB article on the Get Latest operation: http://support.sourcegear.com/viewtopic.php?t=162

[jclausius]

Also note, if you do a GET and ask Vault to overwrite any changed files, the default behavior of the Vault client is to place those changed files into the _sgbak sub-directory. You can retrieve the files from there so you do not lose any info within the files.

[eboykin]

ok, thank you. The KB article helps a lot. It appears that selecting Overwrite plus Prompting for changed files is the same as teh default VSS behavior my group was used to.

I working on a review of our source controll procedures and knowing exactly what the Vault is doing is pretty important for me to be able to do that correctly. I feel I'm on the right track now. Thanks again.