FIX: SET DEFAULT TO .. Causes "Invalid Path or Filename"

 Last reviewed: February 19, 1998
Article ID: Q104796
2.50 WINDOWS kbprg kbfixlist kbbuglist kberrmsg

The information in this article applies to:

  • Microsoft FoxPro for Windows, version 2.5

SYMPTOMS

Issuing the SET DEFAULT TO .. command when the current directory is one level below the root directory causes an "Invalid path or filename" error message.

STATUS

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

MORE INFORMATION

Steps to Reproduce Problem

Assuming FoxPro is installed in a directory named FOXPROW on drive C, issue the following code in the Command window: 

   SET DEFAULT TO C:\FOXPROW\SAMPLE
   ? CURDIR()         && (Current directory is C:\FOXPROW\SAMPLE)
   SET DEFAULT TO ..
   ? CURDIR()         && (Current directory is C:\FOXPROW)
   SET DEFAULT TO ..
After the last SET DEFAULT TO .. command, FoxPro displays an "Invalid path or filename" error message, even though the current directory should be the root directory.

Additional reference words: FoxWin 2.50 buglist2.50
fixlist2.50a errmsg err
msg parent
KBCategory: kbprg kbfixlist kbbuglist kberrmsg
KBSubcategory: FxprgGeneral
Keywords : FxprgGeneral kbbuglist kberrmsg kbfixlist kbprg
Version : 2.50
Platform : WINDOWS
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: February 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.