PRB: Executable Created with FoxPro Starts But Does Not Run

Last reviewed: January 26, 1996
Article ID: Q118558
The information in this article applies to:
  • Microsoft FoxPro for Windows, versions 2.5a, 2.5b, 2.6

SYMPTOMS

When you are executing an .EXE file created with FoxPro for Windows, the .EXE file flashes briefly on the screen and then disappears.

CAUSE

The .EXE file may be reading a CONFIG.FPW file that contains a COMMAND= statement that calls a nonexisting program. The .EXE file will not be able to locate the program and will terminate.

RESOLUTION

Make sure the CONFIG.FPW file does not contain such a command.

MORE INFORMATION

When developing an .EXE file for distribution, many developers copy the .EXE and .ESL files into a separate directory in order to test the .EXE file. When the .EXE file starts up, it acts just like FoxPro and looks for a CONFIG.FPW file in the .EXE's directory. If it does not find a CONFIG.FPW file, the .EXE file looks in the directories that are listed in the MS-DOS PATH statement. When it finds a CONFIG.FPW file, such as the one located in the FoxPro directory, it runs the commands in that file. If a COMMAND= line is in the CONFIG.FPW file and it issues a DO command to run a program, the .EXE file tries to run that program. If the .EXE file cannot find the program, the .EXE file terminates as if a QUIT command were issued.


Additional reference words: FoxWin 2.50a 2.50b 2.60 dk made distribution
kit
executable immediately exit close
KBCategory: kbprg kbprb
KBSubcategory: FxtoolDk


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