FIX: Rollback of a Shared File Rolls to Unexpected Version (157082)
The information in this article applies to:
- Microsoft Visual SourceSafe, 16-bit, for Windows 4.0
- Microsoft Visual SourceSafe, 16-bit, for Windows 4.0a
- Microsoft Visual SourceSafe, 32-bit, for Windows 4.0
- Microsoft Visual SourceSafe, 32-bit, for Windows 4.0a
This article was previously published under Q157082 SYMPTOMS
When 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.
CAUSE
When you Rollback a Shared file, Visual 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.
STATUS
Microsoft 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.
REFERENCES
For more information, please see the following articles in the Microsoft
Knowledge Base:
157813 FIX: Branch or Rollback of Shared File May Cause Corruption
156717 PRB: Rollback of Shared Files Forces a Branch
Modification Type: | Major | Last Reviewed: | 10/15/2002 |
---|
Keywords: | kbBug kbSSafe500fix KB157082 |
---|
|