KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q62216: QBX Hangs Using KEY with Two or More Characters, Then INPUT$

Article: Q62216
Product(s): See article
Version(s): 7.00
Operating System(s): MS-DOS
Keyword(s): ENDUSER | buglist7.00 fixlist7.10 SR# S900517-71 | mspl13_basic
Last Modified: 29-JAN-1991

The program below hangs in the QBX.EXE environment of Microsoft BASIC
Professional Development System (PDS) version 7.00. The problem occurs
when you specify two or more characters in the KEY statement's string
to specify a softkey and follow that with an INPUT$ statement. After
you run the program in the QBX.EXE environment, press the softkey, and
press an additional key, the program hangs after it ends with the
"Press any key to continue" message.

Microsoft has confirmed this to be a problem in Microsoft BASIC PDS
version 7.00. This problem is corrected in BASIC PDS version 7.10.

This is only a problem in the QBX.EXE environment. This program works
correctly when it is compiled to an .EXE program (with either the Near
Strings or Far Strings option).

To work around this problem in BASIC 7.00, do any of the following:

1. Use the INPUT statement (or INKEY$ function in a loop) instead of
   the INPUT$ function.

2. Use only one character in the string for the KEY statement.

The following code sample demonstrates this problem:

   KEY 10, "*" + CHR$(13)   ' Any two or more characters produce problem.
   my$ = INPUT$(1)          ' Press F10 then additional key as input.
   print my$

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.