KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q58026: No QB Error Message If File Listed in .MAK File Does Not Exist

Article: Q58026
Product(s): See article
Version(s): 4.00 4.00b 4.50
Operating System(s): MS-DOS
Keyword(s): ENDUSER | SR# S900119-50 B_BasicCom | mspl13_basic
Last Modified: 31-JAN-1990

When a program that has a corresponding .MAK file is loaded into the
QuickBASIC (QB.EXE) or QuickBASIC Extended (QBX.EXE) environment, all
files listed in the .MAK file are in turn loaded into the environment.
If a file listed in the .MAK file does not exist, an empty module is
created with the name of that nonexistent file. There is no message
generated informing you that a file did not exist.

This is not a problem with the QuickBASIC environment. QuickBASIC
reacts to nonexistent files in a .MAK file the same way it reacts if
the environment is invoked using a nonexistent filename as a command
line argument, for example, QB myprog. In this case, "myprog" will be
created.

This information applies to the QB.EXE environment in QuickBASIC
Versions 4.00, 4.00b, and 4.50, to the QB.EXE environment included
with Microsoft BASIC Compiler Versions 6.00 and 6.00b for MS-DOS, and
to the QBX.EXE environment in Microsoft BASIC Professional Development
System (PDS) Version 7.00 for MS-DOS.

The QuickBASIC environment automatically creates a .MAK file for
multiple-module (multiply-loaded-source file) programs when you choose
the Save All command from the File menu.

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.

Copyright Microsoft Corporation 1986-2002.