BUG: Report to File "Access to File Denied" Error Message

Last reviewed: February 28, 1997
Article ID: Q142092
4.00 WINDOWS kbenv kbbuglist

The information in this article applies to:

  • Microsoft Visual SourceSafe for Windows, versions 4.0

SYMPTOMS

An "Access to File {path\filename} Denied" error message occurs when an historical report is sent to a to a file under Windows 3.x. This occurs only on a 16-bit operating system with the 16-bit version of SourceSafe.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Problem

  1. Run the \Win\Ssexp.exe program under Windows 3.x. This is 16-bit Source Safe and a 16-bit operation system.

  2. Show History of a file.

  3. Click the Report button, and send the report to File.

  4. Verify that the report name does not exist in the directory to which the file is being sent.

  5. Click OK. The error message will appear.

If a file needs to be created, send the results of the report to the clipboard, open an editor, and paste the contents of the clipboard into the editor.


KBCategory: kbenv kbbuglist
KBSubcategory: SourceSafe vbwin
Additional reference words: 4.00
Keywords : SourceSafe vbwin kbbuglist kbenv
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.