FIX: COPY FILE Fails with Error "File Does Not Exist"

 Last reviewed: October 14, 1997
Article ID: Q107364
2.50a WINDOWS kbprg kbfixlist kbbuglist kberrmsg

The information in this article applies to:

  • Microsoft FoxPro for Windows, version 2.5a

SYMPTOMS

The COPY FILE command fails if ".." is used to reference the parent directory of the source file.

STATUS

Microsoft has confirmed this to be a problem in FoxPro 2.5a for Windows. This problem was corrected in FoxPro 2.5b for Windows.

MORE INFORMATION

Steps to Reproduce Problem

In the Command window, issue the following commands: 

   SET DEFAULT TO c:\test
   COPY FILE ..\config.sys TO config.sys
These commands should copy the CONFIG.SYS file from the root directory to the C:\TEST directory, but instead the error message "File c:\\config.sys does not exist" is displayed.

Notes

MS DOS uses ".." to reference the parent directory of the current directory. For example, if you are currently in the C:\DOS directory and want to copy a file to the C:\FOXPROW directory, these two MS-DOS commands would accomplish the same thing: 

   COPY <filename> C:\FOXPROW\<filename>
   COPY <filename> ..\FOXPROW\<filename>
Because C:\ is the parent directory of the C:\DOS directory, ..\FOXPROW is exactly the same as C:\FOXPROW when it is referenced from the C:\DOS directory.

Additional reference words: FoxWin 2.50a buglist2.50a fixlist2.50b errmsg
err msg
KBCategory: kbprg kbfixlist kbbuglist kberrmsg
KBSubcategory: FxenvAutoexec
Solution Type : kbfix

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