We have problem with new Vault client 3.5.1
A user made check out at 12:20 local time
After that the remote date becomes 08:45.
Another user gets the latest version of this file. On his compute the remote file date is 12:45 and local date is 16:20. Though the computer time is 13:00. I.e. it’s future time
In Vault options we are using the Set File Time = Modification.
All clients are in the same timezone: +3
One of clients was 3.5.0, all others 3.5.1
Regards Alexander
time machine
Moderator: SourceGear
You will want your client and server versions to match. Unexpected results can occur when you mix versions.
There was a time related problem that was fixed in 3.5.1. You may wish to check the release notes on that: http://support.sourcegear.com/viewtopic.php?t=6800
Again, it will only help you if you make sure everyone is using the same version.
Once the client and server match, if there continue to be time issues, you can try checking the box that says "Detect modified files using CRCs".
Get back to me if there are still problems after that.
There was a time related problem that was fixed in 3.5.1. You may wish to check the release notes on that: http://support.sourcegear.com/viewtopic.php?t=6800
Again, it will only help you if you make sure everyone is using the same version.
Once the client and server match, if there continue to be time issues, you can try checking the box that says "Detect modified files using CRCs".
Get back to me if there are still problems after that.