How to work with many people on one computer?

thom · Post by **thom** » Thu Nov 04, 2004 4:24 am

We are in testing now of our product (a flight simulator). The sim has its own computer network so we have a development computer which sits between the sim network and the company network. Vault is running on the development computer and fixes are done by developers on this machine by "getting latest" or "checking out" to the sim computers. This seems to mess up vault with respect to the state of the files. The files are continuously going to renegade or unknown. A get latest is very dangerous now as "overwrite unknown files" wipes out other peoples changes. How should we handle this?

dan · Post by **dan** » Thu Nov 04, 2004 8:33 am

If the developers are all using the same working folder, then yes, there would be problems there, as Vault is not designed to allow multiple users to use the same working folders.

Our handling of Unknown files will greatly improve starting with 3.0, but that won't solve the basic problem of the state of files constantly getting overwritten by each user as they login.

The only way to really make this work is that each developer will need their own copy of the source in their own working folder on that machine.

thom · Post by **thom** » Thu Nov 04, 2004 9:07 am

- the working folder is the main load of the simulator. As the final testing is going on the engineers are called in to fix thier stuff. It would be too complicated to work off different builds at this end stage. With source safe we were OK because the only status was checked out, or not checked out.

- Is there anyway to turn off the other states, or better yet have the state information not stored per user but common to all Vault users on that machine. (Note the computer is always logged in as the same windows username but the engineers use thier Vault log in when starting Vault.)

- I noticed that there is an option called
"Store working folder data inside working folders" . Does this do what I want?

sterwill · Post by **sterwill** » Thu Nov 04, 2004 10:00 am

"Store working folder data inside working folders" will start storing all the baseline files and the state file with version information inside the working folders (in an _sgvault subfolder). We don't recommend doing this so multiple users can share working folders, since it's untested, but in theory it should work without problems. There is no per-user information stored with the working folders, just information about each file (current version, merge state, available historic baselines, etc).