Checkout Status for Same User on Two Different Machines

mtanderson · Post by **mtanderson** » Mon Nov 21, 2005 8:47 am

Hi,

I recently upgraded to Vault and my conversion was completely flawless. Kudos to the Vault team for a great install and conversion tool. I was amazed at how well it went. I was able to literally sit down and start working in VS WITHOUT RELOADING any of my local projects. I did not expect this and was surprised when I was able to do so.

Anyways, here's my question....

Like most devs, I have a primary workstation at work and a laptop which I do remote work on. This weekend I VPN'd into my network and did some work on my laptop and left some files checked out. When I returned to the office, I did a refresh on my workstation (for the same user and project) and noticed in Vault that the files were checked out to me on my workstation and I was able to edit them. When I used SourceSafe, it was able to determine if I had a file checked out on a different machine (with the same user) so that it didn't appear as checked out. Is Vault capable of doing this? I tried the "Exclusive Lock" setting on the server but this didn't have an effect (because I am using the same user I suspect).

Thanks,
Mike

dan · Post by **dan** » Mon Nov 21, 2005 10:07 am

In Vault, the file will appear checked out to you, even if you checked it out on a different machine, but you can add a file column (Tools->Options->File List Columns) called Checkout Location which will tell you the local folder where it is checked out. It doesn't have the machine name (although maybe it should), but if you have the file checked out to diff folders on diff machines, it may help. The only way to know for sure is to do a Properties in Vault on the file and look at the Checkout Status pane.

It is probably the case that you can edit the file on your workstation because you've set the Get flag to make all files writable on Get. If this were set to Read, a file would only be set writable on a Checkout, and you have some protection there.

Hope some of this helps...

mtanderson · Post by **mtanderson** » Mon Nov 21, 2005 10:24 am

Hi dan,

I have the get flag set to make files read-only (I'm assuming this is set in the Client Options dialog). I've attached a screen shot of my settings to make sure I'm setting this in the right place.

As you said, I am using the same directory structure on the two machines and I suspected that this was the cause. I guess I would like to see vault use a combination of machine name and directory to determine at the client level if the file is truly checked out to that machine/user.

In SourceSafe, the "location" column is displayed as '[machinename] c:\checkoutpath' and this is what is used to determine status at the local level.

GregM · Post by **GregM** » Mon Nov 21, 2005 10:29 am

The machine name is displayed in that column, but it's displayed after the path, instead of before it like in VSS, and by default the column isn't wide enough to see if for most paths. If you make the column wider, you'll see the machine name.