Article ID: 127993 - View products that this article applies to.
This article was previously published under Q127993
This article has been archived. It is offered "as is" and will no longer be updated.
A Binary file is corrupted after a merge is attempted. There are two scenarios where a merge can occur:
This is by design. SourceSafe cannot read or edit binary files. These files can only safely be edited by the creator application.
To prevent scenario 1, put all binary files in a subproject, and put a Multiple_Checkouts=No in the project header for that subproject. This will turn off multiple checkouts for this subproject only.
For example, you may want to organize your projects as shown in the documentation (User Guide Chapter 2 Overview), with a subproject containing the binary files:
Such that the following would be a subproject header:
$/- | TESTDATA | - BINARIES
[$/TESTDATA/BINARIES]To do this, place the following in the SS.INI file under the subproject header for each user:
Multiple_Checkouts=NoThen only one person can edit that set of files.
To work around scenario 2, use the original application to accomplish the merge manually. In some cases, you can get both versions of the file and use the application utilities to merge the differences.