Q40859: Cannot Use FN at Beginning of SUB or Variable Names

Article: Q40859
Product(s): See article
Version(s): 2.00 2.01 3.00 4.00 4.00b 4.50
Operating System(s): MS-DOS
Keyword(s): ENDUSER | SR# S890124-96 B_BasicCom | mspl13_basic
Last Modified: 15-DEC-1989

In Microsoft QuickBASIC, the FN character combination is reserved for
user-defined functions created with the DEF FN statement. Variable
names, SUBprogram procedure names, and function procedure names
defined with the FUNCTION statement may NOT use FN as the first
characters in the name.

Depending on usage, QuickBASIC can give you errors such as the
following when you incorrectly use FN in a name:

   Duplicate definition
   Invalid identifier
   Cannot start with FN
   Function not defined

The variable, SUBprogram, or FUNCTION should be renamed so that it
does not start with the FN character combination.

This information applies to Microsoft QuickBASIC Versions 2.00, 2.01,
3.00, 4.00, 4.00b, and 4.50, to Microsoft BASIC Compiler Versions 6.00
and 6.00b for MS-DOS and MS OS/2, and to Microsoft BASIC PDS Version
7.00 for MS-DOS and MS OS/2.

More information on the DEF FN statement can be found in the Microsoft
BASIC language reference manual for your version of BASIC or
QuickBASIC.

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.