dotnet academic: When I check out a project to another computer (laptop) under the same
logon, source safe does not give me adequate information that this is the
case. It is an unusual situation in that the project is checked out with
the same ID to a different computer (laptop when I travel, workstation when
not travelling). Once I figured out all I had to do was check it in and
check it out again (I had made no changes to the version on my laptop), but
there was little to tell me that was what was wrong. It said I had checked
it out to a different directory and thus couldn't make changes. Does 2005
improve on this at all?

Hi jamie

The VSS let you check out and/or get last version on any computer you want
as many times as you want.

When is alreday check out you may see the cehck out path so you will see
also the computer name in that path.

VSS tell ypu that the files are check out on another ptah(computer) to warn
you of possible error when your new cahnges may colllide with the new changes
for this new PC.
In the end you could ignore the warning message and chek it from the new
computer as long as you know that nothing could go wrong with your source
file because you used both computers by yourself so you are confident that
evrything is OK to force the CheckIn files from another path than originally
check out.

All these safegaurds are believe me for the better and safer code on all
people involved in the same project

Im using VSS Version 6.0 but also Version 5.0 is having these features

[quoted text, click to view]