Branch existing Shared File

[smahlcrona]

We have recently moved from using VSS to using Vault. In VSS you could remove a shared link from an existing location. I have been unable to identify an equivalent within Vault. In case I'm incredible vague, I'm trying to take a file that is shared in multiple folders, and break the shared link from just one of the shared locations. For example:

File: examplefile.vbs
Share to: Example Folder 1, Example Folder 2, Example Folder 3

Examplefile.vbs located in Example Folder 2 needs to be edited without affecting the shared files in Example Folders 1 and 2. I want to disconnect the share and make the examplefile.vbs in Example Folder 2 a separate file.

How would I do that? Branch only works if you know in advance that you want the file in Example Folder 2 to be different. If you attempt to branch once the file is already in Example Folder 2 you get an error that the file already exists.

Thanks!

Steve

[Beth]

Which file was shared to which?

In Vault, a file that has been shared you can branch and it will act like VSS and just break the connection.

[smahlcrona]

Thanks for the reply Beth.

The file is shared from a working folder. To clarify using my example:

File: examplefile.vbs (located in Working Folder)
Share to: Example Folder 1, Example Folder 2, Example Folder 3

Examplefile.vbs located in Example Folder 2 needs to be edited without affecting the shared files in Example Folders 1 and 2. I want to disconnect the share and make the examplefile.vbs in Example Folder 2 a separate file.

Again, when using branch on file in Example Folder 2 to sever the connection for that file in the that folder an error is reported. The error indicates that the branch fails because a file of the same name is already in the folder.

Thanks again!

Steve

[Beth]

Right-click the file you want to branch and select properties. Does it have any shares listed in the share tab? It sounds like it doesn't actually have a share.

Your working folder should actually have nothing to do with sharing. After a file is placed into Vault, you would use the Share function from inside of Vault to make a share. If you added a file a second time from the same location, that doesn't create a share. Also, adding files doesn't create any kind of link to the file on disk at all. It's the working folder that makes that connection. You can't have more than one Vault location pointing to a particular working folder location.

I might be misunderstanding your set-up, or we might be using the terminology differently. If it sounds like I'm way off base, then could you provide me screenshots and more details?

[smahlcrona]

Beth,

Thanks again for your response, and sorry to further confuse things.

1. Yes, the file shows share locations from the share tab of the properties window.
2. I should have chosen my word choice better. By "working folder", I mean the original source for the shared file within vault. We maintain a directory for the source files where developers will work from. We then share the files to the various builds they may be used. In the case I'm struggling with, one of the builds is very different and changes need to be made to the files for that build without affecting the other builds.

I'll try to get screen appropriate screen shots to demonstrate what I'm seeing. Are there details that you think I'm missing? I'd be happy to provide anything that may be helpful.

Thanks!
-Steve

[Beth]

It might be better if I take a closer look. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?