PRB: Cannot Start VFP from Run Open Line If Space in Path

Last reviewed: November 1, 1996
Article ID: Q158404
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, version 5.0

SYMPTOMS

If Visual FoxPro is installed in a directory with a space in the folder name, Visual FoxPro cannot be started from the Run Open line in Windows 95 or Windows NT.

One of two things happen: either a directory screen is displayed or a message like the following appears:

   Cannot find the file 'C:\Directoryname'(or one of its components). Make
   sure the path and file name are correct and that all required libraries
   are available.

The directory screen or folder appears when the first word (used prior to the space in the name) matches the name of an existing folder. For instance, if Visual FoxPro is installed in the My vfp folder and you have another folder called My, the My folder is displayed.

CAUSE

Visual FoxPro is installed in a directory with a space in the folder name.

WORKAROUND

If you need to start Visual FoxPro from the command line, do one of the following:

  Enclose the entire path in quotes.

  -or-

 Make sure there are no spaces in the path to the Visual FoxPro
 executable.

STATUS

This behavior is by design.

This problem is not specific to Visual FoxPro. Other programs such as Word do not start from the Run Open line if there is a space in the path name.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Place a space somewhere in the path to Visual FoxPro.

  2. Start Visual FoxPro from the Open line in the Run window.


KBCategory: kbenv kbsetup kbother kbprb
KBSubcategory: FxenvGeneral FxsetupGeneral
Additional reference words: 5.00 vfoxwin kbdsd



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: November 1, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.