>Well, we have poured over the MSN article, and experimented a little. When we unpin a program in the development copy, and then make a modification in it, the modification still is reflected in the production copy of the project. That program is pinned in the production copy. We just end up with a new version of the modified program in the production copy.
>
>We don't want the changes to flow back and forth like that. We want changes in development to NOT show up in production. Changes in production (God forbid!) to fix some future bug SHOULD flow down to development. And after an afternoon of experimentation, we're a bit confused. Any tips?
>
>Marie

The way we manage various projects is to have separate 'sourcesafe' projects for each area. (Dev-Test-Prod) The code is shared between the 3. Test and Prod are pinned. If you do a getlatestversion in a pinned sourcesafe project you will get the version that is pinned in that project. The unpinned Dev project can be modified multiple times and Prod will never see those changes unless you unpin the Prod project and getlatestversion.

At some point you may need to decide which direction your development effort is going to flow. What I just described should work, beyond that I guess I would have to be there. :)