Version Control Best Practice

Hi Guys,

Just wondered if there was a certain best practice when dealing with version control.

At the moment we use VSS and have a shadow copy ofall the files on the server. When we check the files out of VSS it copies it into our writable folder. In effect we have an empty directory structure each that we use for editing in and then moving stuff back to a single read only folder structure. (If that makes sense).

Our propath goes to the project folders first and then to the central shadow folders so if we check something out we use our local copy while everyone else uses the shadow copy. (I hope this is making sense).

Anyway, I have been looking at migrating to OEA and was also thinking about integrating version control with something like Subversion. I have been trying to get the OEA debugging working and it seems to work ok until it calls a procedure that isn't in the project folders. To get round this we would ideally have an entire copy of all the program files on our editable directory as well as the shadow copy on the server.

Can anyone shed any light on best practices with version control and whether something like subversion can deal with the potential act of more than one person editing the same file at the same time.

Thanks for any help

Oliver