>First of all, nice to *see* you again! I'm finally off the MS newsgroups,
>since we decided to switch over to the UT in our shop. Hope you've been doing
>well!

Yes! The Unholy Trinity is re-united! :-)

>The way I understood the problem was that after the 2 developers' projects
>were set up under VSS, one of them added a file to the project and source
>control.
>The other then did not get the updated file.
>The only thing we have found that works to *automatically* get new files is to
>re-join the source control project. We don't really want to do that, so we
>have to manually copy the file(s) over to the development machine, add them to
>the project, add them to source control, get the source controlled version
>(when it tells you that it's already under source control).

If you don't have Multiple Checkouts enabled, you probably need to follow these steps.

1) If you can't turn on Multiple Checkouts from the VSS interface, go into the VSS database (SrcSafe.ini) and add the following lines (using the name of your project instead of mine:

[$/myVFPProj]
Multiple_Checkouts = yes

2) Go into the SourceSafe explorer and check the PJM file in: it will probably be checked out exclusively to one of your developers.

3) Have the developers each open the project. When you refresh the view in the SS Explorer, you should see the PJM file checked out to each of them.

From this point on, Update Project List should work for both of them.

>We also haven't got pinning or rolling back to work with VSS, either.
>Have you ever got these to work?

I've rolled back individual files, if that's what you mean... I'm still not sure about pinning, though.