FIX: SourceSafe Command Line Fails to Create Output File

Last reviewed: August 25, 1997
Article ID: Q129190

The information in this article applies to:

SourceSafe for MS-DOS, versions 3.04, 3.1
SourceSafe for Windows, versions 3.04, 3.1
SourceSafe for Macintosh, versions 3.04, 3.1
SourceSafe for Windows NT, versions 3.04, 3.1

SYMPTOMS

SourceSafe fails to create an output file when executing the Checkout Command. This occurs when the file specified to be checked out is not a valid file in the current project or the specified path does not exist.

The following won't create an output file if the filename doesn't exist in the current project:

      SS CHECKOUT test -o&@filename.txt

The ampersand (&) and at (@) characters make no difference.

STATUS

Microsoft has confirmed this to be a bug in SourceSafe version 3.1 for Windows, Windows NT, MS-DOS, and Macintosh. This problem has been corrected in Visual SourceSafe version 4.0.

Keywords          : SourceSafe SRCSAFE SS vbwin buglist3.10 fixlist4.00 kbbuglist
Version           : 3.04 3.10
Platform          : MACINTOSH MS-DOS NT WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: August 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.