FIX: Rollback of a Shared File Rolls to Unexpected VersionLast reviewed: January 28, 1998Article ID: Q157082 |
The information in this article applies to:
SYMPTOMSWhen you Rollback a Shared file, the resulting version number may appear to be incorrect. For example, if your file contains 8 versions, and you elect to Rollback from version 8 to version 7, the History window will indicate that you rolled back to version 8, not 7 as expected.
CAUSEWhen you Rollback a Shared file, SourceSafe forces a Branch to occur. The additional version number is a result of the Branch that takes place when a shared file is rolled back.
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem has been fixed in Visual SourceSafe 5.0.
MORE INFORMATIONSteps to Reproduce Problem
REFERENCESFor more information, please see the following articles in the Microsoft Knowledge Base:
ARTICLE-ID: Q157813 TITLE : FIX: Branch or Rollback of Shared File May Cause Corruption ARTICLE-ID: Q156717 TITLE : PRB: Rollback of Shared Files Forces a Branch Keywords : ssusage kbusage Version : 4.0,4.0a,5.0 Platform : WINDOWS Issue type : kbbug Solution Type : kbfix |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |