We use Vault 3.0.1 and we setup the client to a VSS style (check-out check-in).
Here are some anoying glitch our programs got when using Vault;
Problem 1
=======
- File is renegate
- Do a get latest on the file
- the local file is updated, but the program don't compile.
- We compare the local and the network file, we realise that the last lines that where added on the network are added in the local file 10 lines later in the file (at the wrong place).
- Add to do a get latest overwrite to fix the problem.
This is particularely dangerous if the programs still compile even if the lines aren't added at the same place.
Problem 2
=======
Even if we use the "use CRC to compare files" option, a lot of files are getting the renegate status sporadically even if those files are identical (network VS local). To remove the renegate status, programmers have to do regularely some GetLatestVersion. They spend times on it and they start to be frustrated of doing it repetively.
![Mad :x](./images/smilies/icon_mad.gif)
We have this problem from the start and I investigated a lot to get the source of the problem. At first it was one of our program that where modifying the date of the files, we correct the problem but the bugs still sticking, but less bad. Now I have some indices that makes me think it is Visual Studio, but not for sure.
Anyway, whatever is the source, if you check the CRC of the content of the file, there is no excuse to pop a Renegate status if files are identical and the dif app tells too that they are identical.
Problem 3
=======
- File get Old status (without apparently logical cause)
- Do Get Latest on it
- operation failed (on msg window)
- Get Latest Overwrite (sometimes its ok from here)
- the file get the "Needs Merge" status
- Do again a Get Latest Overwrite
- the status get backs to normal.
In all step, a compare files showed here that they where identical. This pattern showed up since we upgraded to the 3.01 version.
Problem 4
=======
We have a lot of problem too about the "Read Only" status of files. I couldn't note for you a specific pattern about this problem, but sometimes files don't get writtable when we check out or don't get Read Only when we check in. This is kind of dangerous...
Ending Notes
========
I activated the log in Vault so that when a bug occur, I can send it to you. But I couldn't find the log file in the temp directory. Where is this log file and what is it's name format?
From the start, I apreciated a lot the service you gave me in the support, even when I posted in the standard support (not the gold). Every time the maximum delay I got is less than a day, your service is really exellent and a lot of user seems to appreciate it. It's one of the major argument that leads us to buy your product.
Safe your respect, the only think that tire me and the programmers it's all those little glitches, they scares us because we don't feel that the product will take care of the source. Trying to get the causes is painfull because there is not a lot of indices and most anoying, it cost us time that we don't have.
I stay at your service to get as much as information needed about it and I hope that these bugs will be catch asap.
Thanks again for your kindness and your good support,
Regards,