BUG: FoxPro/FoxBASE+ Not Using Code Edited w/External Editor

• Microsoft FoxPro for MS-DOS, versions 1.0, 1.01, 1.02, 2.0, 2.5, and 2.5a
• Microsoft FoxBASE+ for MS-DOS, version 2.1

SYMPTOMS

When you use the RUN command or the TEDIT parameter in the CONFIG.FP file to launch an external editor, FoxPro or FoxBASE+ sometimes runs the code in the buffer instead of the modified source code on disk.

CAUSE

FoxPro for MS-DOS and FoxBASE+ for MS-DOS maintain a buffer of the most recently executed programs. In some cases, when an external editor is used to modify an application, FoxPro or FoxBASE+ does not recognize the changes to the source code on the disk and runs the code in the buffer.

RESOLUTION

Before using the RUN command or the TEDIT parameter in the CONFIG.FP file to launch an external editor, use either the CLEAR PROGRAM or FLUSH command to remove the last executed program from memory. Doing so ensures that the program that runs is the updated program. The CLEAR PROGRAM command clears the buffer and causes FoxPro or FoxBASE+ to read the file in from the disk. FoxPro or FoxBASE+ then recompiles the source code because the .FXP file is out of date.

STATUS

Microsoft has confirmed this to be a problem in FoxPro 1.0, 1.01, 1.02, 2.0, 2.5, and 2.5a for MS-DOS and in FoxBASE+ 2.1 for MS-DOS. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

NOTE: This problem does not occur in FoxPro 2.5 for Windows.

MORE INFORMATION

For example, to use the MS-DOS Editor as the FoxPro editor, place the following command in the CONFIG.FP file:

   TEDIT=C:\DOS\EDIT.COM

NOTE: The specified editor must be able to save the file in ASCII text format. The TEDIT specification does not affect editing a memo field with the MODIFY MEMO command. A memo field is always edited with the default FoxPro editor.