Microsoft KB Archive/131452

{| 3.04 3.10 4.00 5.00 | 3.04 3.10 4.00 5.00 | 3.04 3.10 4.00 WINDOWS            | WINDOWS NT          | MS-DOS kbusage kbprb The information in this article applies to:
 * width="100%"|


 * Microsoft Visual SourceSafe, versions 4.0, 5.0
 * Microsoft SourceSafe for Windows, versions 3.04, 3.1
 * Microsoft SourceSafe for MS-DOS, versions 3.04, 3.1
 * Microsoft SourceSafe for Windows NT, versions 3.04, 3.1

SYMPTOMS
If a SourceSafe file has been shared and then separated, a rollback doesn't restore the share information between files, but it does restore the file contents.

CAUSE
The ROLLBACK command is very useful for undoing changes to a file within a project. The one caveat to this is that the ROLLBACK command affects the contents of the file but not the status of the file. If an item was shared at version 20, separated at version 30, and rolled back to version 25, the data appears as it did in version 25, but the file is still separated even though the file was shared at this version previously.

STATUS
This behavior is by design.

Steps to Reproduce Behavior

 * 1) Create two projects (Proj1 and Proj2).
 * 2) Add any file (File1) into Proj1.
 * 3) Update the file twice so that there are some history items for the file. File1 should be on v3.
 * 4) Share the file into Proj2. Make note of the links and paths.
 * 5) Update the file two more times. File1 should be v5.
 * 6) Separate the file in Proj2. Make note of the links and paths again.
 * 7) Roll back the file to v3.

The links and paths will be the same as in step number 6, but the file is now as it was at version 3.
 * }

-

Last reviewed: February 28, 1997

© 1998 Microsoft Corporation. All rights reserved. Terms of Use.