Status of files vary by user

[kcmod]

My department uses vault for important files that get updated often. We do this so that only one person can make changes to files on a shared drive at a time and to allow us to revert back to an older version if something happens to the file. Lately we have noticed many vaulted files that show a different "status" for the same file for different users. For example, a file that shows no status code for me, shows a status of "missing" for another user for the same file. If the working file is at the same location on a shared drive how can the status be different for different users?

Thanks!

[lbauer]

If the working file is at the same location on a shared drive how can the status be different for different users?

Yes. This is why we don't recommend multiple users using the same working folder, as file status can be unpredictable.

Working folder status is determined by comparing the file in the working folder to the baseline in the Vault client's cache/baseline folder on the client machine.

If a user has no working directory set for a particular repository folder, the status is "missing."

If UserA checks out a file and modifies it, UserB's Vault Client will see that file as Renegade, because for that user, the file is modified, but not checked out to UserB.

It might help if user's store the baselines in the working folder. This setting is in the Vault Client under Tools->Options->Local Files->Cache location->Store working folder state/baseline files.