Issue w/ Get Lastest + Overwriting Local File + Checkout

[tresstylez]

One of our developers noticed a difference in the way Vault handled the case where she is Getting Latest for a particular file.

Previously, she was able to Get Latest, and overwrite the local file on her system without Checking Out the file. Now she says she has to actually check the file out before overwriting the local file.

Is this something that changed in the client at some point? Or, maybe an admin setting I'm overlooking? Any help is appreciated! Thanks.

jg

[Beth]

Which version of Vault are you using?

A Get Latest shouldn't require a check-out. What is the file status prior to the user performing a Get Latest?

[tresstylez]

Version is 5.0.4.

File Status before the Get Latest is Merge or Edit.

[Beth]

What settings does your user have under the Vault Tools - Options - Concurrent Development Style?

[tresstylez]

Auto-commit is CHECKED.
Require Check Out is UNCHECKED.
Always request exclusive locks is UNCHECKED.

[Beth]

On the drop-down on the same page, is the Make Writable setting set to read-only?

So far with the same settings, I can't reproduce the issue, but my Make Writable setting is set to read-only.

If your settings are the same, then we might need to take a closer look. If that's the case, then would you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?