Vault treating files as read-only?

Colen · Post by **Colen** » Thu Apr 27, 2006 8:09 pm

Hi,

I'm evaluating Vault because we want to stop using the terrible nightmare that is sourcesafe. So far I've found one weird bug. I'm using server v3.1.8 and client v 3.1.8.

I put some random files into a vault database to see how it would work. I switched the "Make writable:" setting to "Make all files writable". Then I got the latest version of all those files into a new (empty) working folder.

I choose a file at random, open it in notepad (from explorer, not from the vault interface) and add one line to it. then I save and close. Vault correctly marks the file as "Renegade".

I right-click and "Show Differences", choose the default "last version retrieved" and click ok. The baseline and working versions of the files are both shown here. Except that they're BOTH marked as read only.

I can understand that the baseline is read only. But why is the working version read only? If I right-click the file in Explorer, it isn't read only. Why is this happening? When the file is incorrectly marked as read only like this, I can't use the DiffMerge interface to make changes.

Note that neither explorer nor notepad think the file is read only - only vault seems to.

Any ideas?

GregM · Post by **GregM** » Fri Apr 28, 2006 6:27 am

There's a knowledge base article about this.

http://support.sourcegear.com/viewtopic.php?t=2670

Colen · Post by **Colen** » Fri Apr 28, 2006 1:27 pm

Oh, thanks! I'll make that change. But if the files are read-only, how are you supposed to merge them into each other?

Post by **jclausius** » Fri Apr 28, 2006 1:37 pm

Colen wrote:Oh, thanks! I'll make that change. But if the files are read-only, how are you supposed to merge them into each other?

Usually the files are writable, and do not have their attributes set to read-only.

The /ro flags control the merge tool's "read-only" mode.

Colen · Post by **Colen** » Fri Apr 28, 2006 3:09 pm

Right, I'm just trying to work out why the merge tool is read only by default. Surely it'd be more useful to have it not read only?

Thanks.

Post by **jclausius** » Fri Apr 28, 2006 9:02 pm

My guess is the setting will prevent accidental saves of a file - losing one's work.

Regardless, it is just a setting. Feel free to modify these settings to adapt to your environment.