>Douglas,
>
>I agree completely. I don't think, we made a wise decision while back, when we decided to not use Source Safe. We have this situation here: our main project called JobControl works with lots of applications, each of them is responsible for the specific task. For instance, during my work here (2 years +) I designed (or took in my ownership and then modified) 15 applications, not talking about lots of reports, UDFs, XForm transformations, etc. Usually each developer is responsible for the particular application.
>
>Still the process of updating and maintaining is very painful and combersome.
>
>My colleague is supposed to write a special migration utility...

Nadya;
We went through that pain too! In most of our work, our developers are maintaining legacy code, and having individual responsibility for each application. There are a couple of very large applications however, that have several developers working on them jointly, and these are the ones where we use VSS. On the smaller tasks, we do not have them in VSS, but use a clearly defined backup policy. This probably sounds like a hodge-podge, but it is really set up about as efficiently as we can, based on our experience of having to repeat work done when one stepped on another and overwrote a couple of days work.