KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q30372: "Type Mismatch" When "INPUT1" Is Elementname in TYPE Statement

Article: Q30372
Product(s): See article
Version(s): 4.00 4.00b 4.50
Operating System(s): MS-DOS
Keyword(s): ENDUSER | buglist4.00 buglist4.00b fixlist4.50 B_BasicCom | mspl13_basic
Last Modified: 31-JAN-1990

A variable "type mismatch" error improperly occurs if the reserved
word "INPUT" is embedded in an elementname in a TYPE...END TYPE
statement.

Microsoft has confirmed this to be a problem in QuickBASIC Versions
4.00 and 4.00b and in Microsoft BASIC Compiler Version 6.00 for MS-DOS
and MS OS/2 (buglist6.00). This problem was corrected in QuickBASIC
Version 4.50, in the compiled version of Microsoft BASIC Compiler
Version 6.00b (fixlist6.00b), and in Microsoft BASIC Professional
Development System (PDS) Version 7.00 for MS-DOS and MS OS/2
(fixlist7.00).

The same syntax does not fail when it is not in a TYPE elementname.
For example, the following two-line program runs properly:

   f.input1 = 123.2
   PRINT f.input1

Please note that the TYPE...END TYPE statement is not supported in
previous releases of the QuickBASIC compiler.

To work around this problem, avoid using reserved words embedded
within names used in the TYPE...END TYPE statement.

The following is a code example:

TYPE checkout1
       numa AS INTEGER
       input1 AS STRING * 10    'works ok if input1 is changed to out1
END TYPE
DIM f AS checkout1
f.input1 = "abcdef"
PRINT f.input1

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.