Microsoft KB Archive/129923

{|
 * width="100%"|

-

The information in this article applies to:


 * Microsoft FoxPro for Windows, version 2.6a

-

SYMPTOMS
Compact executables created in FoxPro for windows are expected to run independently when installed in a directory that contains the FoxPro library file (FPW2600.ESL). However, some executables that run within the FoxPro development environment fail to run when moved to a separate directory in windows. Double-clicking the file doesn't generate any result, and there is no error message to indicate its failure to run.

CAUSE
One possible cause of these symptoms is the naming convention used for the executable file. If the name of the executable file is identical to a Windows system file such as USER.EXE, GDI.EXE, or KERNEL.EXE, the executable won't run outside the FoxPro development environment. These names are not reserved words in FoxPro, however, users who give their application similar names will be able to run them within FoxPro but will have problems in Windows.

RESOLUTION
Rename the application file.

STATUS
This behavior is by design.

Steps to Reproduce Behavior
Create an executable named USER.EXE from any project (.PJX) file in FoxPro for Windows.

Create a new directory in Windows and move the following files to that that directory:


 * USER.EXE (the executable created from the project file)
 * FPW2600.ESL (the FoxPro library file)
 * Any other files required to run the executable such as .DBF or .CDX files.

Try running the Executable file by double-clicking it in File Manager.

NOTE : This condition is true for executables with these names created in FoxPro for MS-DOS that run under Windows from the File Manager. However, the problem will not occur if the same file is run from the MS-DOS prompt. Additional query words: FoxWin will not run

Keywords         : kbenv FxotherGeneral Version          : 2.60a Platform         : WINDOWS Issue type       :
 * }