I've just set up Visual SourceSafe 2005 (server-based) to do source control
on my Access 2003 (Access 2000 file format) front-end application. I was very
impressed with how easy it was to add my project to VSS.
I labelled the production version of the application, then proceeded ...

I'm trying to lay out a plan for upgrading Visual Source Safe 6.0d to 2005,
and Visual Studio 03 to 2005 but I'm not finding any clear
information/documentation either on MSDN or in the readme.  Specifically,
I'm trying to figure out the best upgrade order, the one which is least ...

This could sound like a paranoia but it really matters to me.
Can you tell me if I need to "get latest version" each time I check out a
file?
what if I leave the project open and shut down the PC and someone edits some

I have existing VB.Net 2005 projects I'm wanting to add to VSS 2005.  All myt
projects have been built to put solution file seperate from project.
My project is at:
c:\vbsource\projecta

I overheard that there was a new version control product from
Microsoft, but I can not remember the name. (I heard the name in a job
interview, as I rejected that offer, I can not go back to ask what was
the name now).

I've checked in lots of changes in one project, but I realized that there
could be errors, so I thinked that going back to a previous version could be
a good idea.
But I'm not very sure about how to do it: I was thinking that I could...