SourceSafe actions resetting Working Folder

[kinook]

The only command-line option that should change the VSS working folder for a
user is the WorkFold command. If you're not using that and the working folder
is getting changed by a VSS operation, there may be a bug in VSS, since the
SourceSafe action in VisBuildPro actually calls its command-line program
(ss.exe) to perform the operation. You might also look into the
Force_Dir/Force_Proj variables (or equivalent settings at Tools | Options |
Command Line Options in the VSS Explorer) -- I don't know if those settings
would have any effect on this behavior or not. Finally, as a workaround, you
may want to consider creating a separate 'build' user to be used by your
automated build (which should prevent your own working folders from being
affected).