TIMESTAMP issue...

grosin · Post by **grosin** » Fri Jun 09, 2006 12:19 pm

I'm using Vault in the TIMESTAMP mode. My situation is kind of wacky, but I sometimes take stuff home to work on it. So basically at the end of the work day I check in, I then zip up my source directory using WinZip 10, and in the morning unzip over my directory when I come in... the problem is when I open vault to merge my changes, it shows that files are "edited" that I haven't touched. Me and my build guy tracked it down to a rounding error somewhere. The filetimes on some files are off by a single SECOND. Is there any way to work around this on the vault side? I know there is the CRC option, but isn't that going to be really slow?

lbauer · Post by **lbauer** » Fri Jun 09, 2006 12:27 pm

I know there is the CRC option, but isn't that going to be really slow?

It might be *slower*, but not necessarily so slow that it will bring production to a halt. You might try that, since by default, Vault does use timestamps to determine if files have changed.

Another thought -- Vault is made to be used remotely. Can you access your Vault server from home? If so, you could checkout files, edit them, and check them in from home, making them available to you to check out or get at the office.