Microsoft KB Archive/50219

= Reasons for &quot;File Not Found&quot; Error Using $INCLUDE Metacommand =

Article ID: 50219

Article Last Modified on 11/21/2006



This article was previously published under Q50219



SUMMARY
The text file specified in a $INCLUDE metacommand must exist on disk, or the message &quot;File not found&quot; appears.

You get the &quot;File not found&quot; message unless you do one of the following:


 * 1) Qualify the filename with an explicit directory path in the $INCLUDE statement.
 * 2) If an unqualified filename is specified in the $INCLUDE statement, the file must be in the current directory or the root directory. In addition, QuickBasic Version 4.50 and Microsoft Basic Professional Development System (PDS) Version 7.00 are enhanced to recognize the DOS INCLUDE environment variable (for both QB.EXE, QBX.EXE and BC.EXE) for unqualified $INCLUDE filenames. Both of these versions also let you set additional $INCLUDE file paths in the Options menu.

The following products DON'T recognize the DOS INCLUDE environment variable to search for unqualified $INCLUDE filenames: Microsoft QuickBasic Versions 1.00, 1.01, 1.02, 2.00, 2.01, 3.00, 4.00, and 4.00b for MS-DOS, and Microsoft Basic Compiler Versions 6.00 and 6.00b for MS-DOS and MS OS/2.



MORE INFORMATION
If the file isn't found, a &quot;File not Found&quot; error is flagged on the REM in the REM $INCLUDE: 'filename' statement (instead of on the filename in the single quotation marks in QuickBasic 4.00, 4.00b, and 4.50 and in QuickBasic extended shipped with Microsoft Basic PDS Version 7.00).

To create an include file while in the QuickBasic QB.EXE 4.00, 4.00b, or 4.50 editor, or the QBX.EXE editor, use the Create File command on the File menu and select Include. Then when you try to execute the program in the editor, it will inform you to save the Include file before execution can occur, preventing the &quot;File not Found&quot; error.

Additional query words: QuickBas BasicCom

Keywords: KB50219

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.