>Hi Mike ,
>what is <snip> ?
>

SNIP means I cut out stuff that didn't apply.

>>>It is just matter of having sound policies about submiting (overwriting) files on master copy. This could be either one apointed senior in a role of 'class librarian' , if team has young unexperenced members, or simply caution/torough testing if team is seasoned & well organized.
>
>>Someone should have the release code (final set of code used to produce the exe for release). A backup of the release code should be kept on the server. Having one person responsible for collecting the code reduces the team's productivity. It becomes a log jam. That's why source control products exist.
>
>
>Well, since I never worked with big US style software enterprises,
>I cannot (& I did not) say that what I described can apply there.
>Bigger software/other businesses probably hv bigger problems & issues all together.
>
>But I do know why source control exist, I am just happy that I don't have to use it just yet.
>Thks for warning me about logs/jams/team pruductivity issues ahead.
>Will get myself 'ready'
>

I only use source control to keep the history of all the changes. That is very useful even if you work alone.