BUG: MODIFY FILE...NOMODIFY WINDOW Disables Command Window

ID: Q108481

The information in this article applies to:

SYMPTOMS

In FoxPro for Windows, the command 

   MODIFY FILE <filename> NOMODIFY WINDOW <undefined window>

   -or-

   MODIFY FILE <filename> NOEDIT WINDOW <undefined window>
causes FoxPro to return the error message "'<undefined window>' not defined" and does not allow further entry in the Command window.

RESOLUTION

To avoid this problem, remove the NOMODIFY or NOEDIT clause.

STATUS

Microsoft has confirmed this to be a problem in FoxPro versions 2.5, 2.5a, 2.5b, and 2.6 for Windows. 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 version 2.5b for Macintosh.

MORE INFORMATION

Steps to Reproduce Problem

In the Command window in FoxPro for Windows, type either of the following commands: 

   MODIFY FILE <filename> NOMODIFY WINDOW <undefined window>

   -or-

   MODIFY FILE <filename> NOEDIT WINDOW <undefined window>
FoxPro for Windows returns the error message "'<undefined window>' not defined." A default text editing window appears containing the file specified in the MODIFY FILE command. At this point, you can no longer enter any information in the Command window.

If you issue these commands in FoxPro for MS-DOS, FoxPro displays the error message "WINDOW '<undefined window>' has not been defined." The text editing window appears, and you can still enter commands in the Command window.

If you issue these commands in FoxPro for Macintosh, FoxPro displays the error message "WINDOW '<undefined window>' has not been defined." No text editing window appears, and you can still enter commands in the Command window.

Additional reference words: FoxWin 2.50 2.50a 2.50b buglist2.50 buglist2.50a buglist2.50b 2.60 buglist2.60 KBCategory: kbprg kbbuglist KBSubcategory: FxprgGeneral

Last Reviewed: June 27, 1995