Vault undoing check-outs on shared files without warnings

[gdenning]

If I have a file shared between two directories (let's call them directories A and B), and check out the file in directory A, the file also shows up as checked-out in directory B. This is fine, and as one would expect, the "Check In" option is grayed out if you try to check in the file in directory B. However, this is not the case in the VB6 SourceGear integration. The file appears as checked-out in the project in directory B, and if you forget that you checked out the file in directory A, and try to check it in, Vault automatically undoes the check-out (because it detects no changes to the file in directory B) and the file becomes "renegade" in directory A. No warnings are given by Vault even though the following "Show Warning" setting is enabled:

"When Checking-In shared files from a location other than the one that they were Checked-Out to"

This bug has already caused me to have to manually recover my changes a number of times from the backup directory. Is there anything that can be done about this? Ideally, it would be nice if shared files didn't appear as checked out in the SourceGear integration unless they were actually checked out in that directory.

[lbauer]

This is a known issue and we have bugs logged to display the warning and also to handle this situation better. We hope to address them in Vault 4.0, due out later this year.