BUG: SET('KEYCOMP') Produces "Invalid Set Expression" Error

 Last reviewed: April 18, 1995
Article ID: Q114198
The information in this article applies to:
  • Microsoft FoxPro for MS-DOS, versions 2.5b, 2.6

SYMPTOMS

When the 'KEYCOMP' parameter is passed to the SET() function (as shown in the following example), an "Invalid Set Expression" error message is produced: 

   ? SET('KEYCOMP')

RESOLUTION

SET KEYCOMP is not a valid set expression under FoxPro for MS-DOS. To visually emulate the SET KEYCOMP behavior, implement the following code: 

   DO CASE
   CASE _WINDOWS = .T.
      KEYCOMP = "Windows"
   CASE _MAC= .T.
      KEYCOMP = "Mac"
   CASE _DOS= .T.
      KEYCOMP = "DOS"
   ENDCASE
When this code is run under FoxPro for MS-DOS, the "DOS" option will be returned to the screen. Unfortunately, the keyboard navigation cannot be changed from the default MS-DOS command.

STATUS

Microsoft has confirmed this to be a problem in FoxPro versions 2.5b and 2.6 for MS-DOS. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

In FoxPro for Windows and FoxPro for Macintosh, SET('KEYCOMP') can be used to determine what type of keyboard navigation was chosen with the SET KEYCOMP command.

Additional reference words: FoxDos 2.50b 2.60 errmsg err msg buglist2.50b
buglist2.60
KBCategory: kbprg kberrmsg kbbuglist
KBSubcategory:

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.

Last reviewed: April 18, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.