PRB: Visual SourceSafe Occasionally Saves .FRX File as Text

Last reviewed: February 28, 1997
Article ID: Q155054
4.00 WINDOWS kbinterop kbprb

The information in this article applies to:

  • Microsoft Visual SourceSafe, 16-bit and 32-bit, for Windows, version 4.0
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0

*********************************************************************

**                           - WARNING -                           **
**     THE INFORMATION BELOW IS PRELIMINARY AND HAS NOT BEEN       **
**     CONFIRMED, EDITED, OR TESTED BY MICROSOFT. USE ONLY         **
**     WITH DISCRETION.                                            **
*********************************************************************

SYMPTOMS

Visual SourceSafe will sometimes save a Visual Basic form's binary file (.FRX) as text rather than binary, depending on the objects placed on the Visual Basic form.

If this "text" version of the .FRX file is checked out, and the program is run or the form is modified, an "Illegal Operation" error will result in either OLE32.DLL, SSSCC.DLL or KERNEL32.DLL.

NOTE: This problem is not reproducible in Visual Basic 4.0a/Visual SourceSafe 4.0a.

RESOLUTION

To force a particular file type to be treated as binary, the following line should be added to the SRCSAFE.INI file on the server:

   Binary_Masks = *.frx

This .INI information can be added by using the "File Types" tab found by choosing Options from the Tools menu.

STATUS

WARNING: The information in this article has not been confirmed or tested by Microsoft. Some or all of the information in this article has been taken from unconfirmed customer reports. ANY USE BY YOU OF THE INFORMATION PROVIDED IN THIS ARTICLE IS AT YOUR OWN RISK. Microsoft provides this information "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

REFERENCES

For additional information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q132892
   TITLE     : SourceSafe May Modify Some Files


KBCategory: kbinterop kbprb
KBSubcategory: ssafe vbwin vb4win vb4all vb ssvb
Additional reference words: 4.00
Keywords : ssafe ssvb vb vb4all vb4win vbwin kbinterop kbprb
Version : 4.00
Platform : WINDOWS


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: February 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.