Shared files and working folders

[smpete]

I've recently switched to Vault and the limitation of not allowing more than one Vault folder assigned to a working folder has caused a major road block for me. We have shared files between different applications. In Vault we create a folder for each application and create a share at the file level for our shared files. When I'm working on a task that will require making a change to a shared file, I normally would set the same working folder for each application (this was in my previous source control application called Evolution). This would allow me to compile all the applications with the modified file in the same working folder. I can no longer do this in Vault and I haven't figured out another way to accomplish the same process. I don't want each of the applications in there own folder because only the first application that I work on will have the shared file checked out and the other applications won't have my modified file yet because the shared file will not have been checked in yet. I can't check it in, because I'm still in testing of my modifications and I can't let other developers have access to the modified shared file yet.

Anyone have any suggestions on a different process I should be using to accomplish the same result?

[Beth]

One thing you could try is unsetting the working folder for one area when you want to set that working folder to a different area. When you switch, the status will first be Unknown, but performing a Get with a Do Not Overwrite/Merge Later will reset the statuses. If your concern is time in unsetting and setting, you could write a few scripts ahead of time and just run them when you are ready to check the next project with those files.