KEYMATCH() Syntax Differs Between FPW and FPD Help Files

 Last reviewed: February 16, 1996
Article ID: Q117319
The information in this article applies to:
  • Microsoft FoxPro for Windows, version 2.6
  • Microsoft FoxPro for MS-DOS, version 2.6

SUMMARY

The syntax for the KEYMATCH() function is documented differently in the online Help files of FoxPro for Windows and FoxPro for MS-DOS.

The FoxPro for Windows Help file gives the following syntax for the KEYMATCH() function: 

   KEYMATCH(<index key> [, <expN1> [, <expN2> | <expC>]])
However, the FoxPro for MS-DOS Help file gives the following syntax: 

   KEYMATCH(<index key> [, <cdx file>] , <expN1> [, <expN2> | <expC>])
The syntax shown in the FoxPro for Windows Help file is correct.

MORE INFORMATION

The KEYMATCH() syntax shown in the FoxPro for Windows Help file is similar to the syntax in dBASE IV version 2.0: 

   KEYMATCH(<index key> [, <expN1> [, <expN2> | <expC>]])
The brackets indicate that you can use any one of the following 

   ?KEYMATCH(<index key>, <expN1>)

   -or-

   ?KEYMATCH(<index key>, <expN1>, <expN2)

   -or-

   ?KEYMATCH(<index key>, <expN1>, <expC>)
where <expN1> is the index tag number, <expN2> is the work area number, and <expC> is the work area alias.

NOTE: Issuing ?KEYMATCH(<index key>, <expC>) will generate an "Invalid Function Argument" error message because this syntax is incorrect.

Additional reference words: FoxDos FoxWin 2.60 docerr foxhelp.hlp
foxhelp.dbf on-
line
KBCategory: kbprg kbdocerr
KBSubcategory: FxinteropDbase

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: February 16, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.