PRB: LOCATE FOR Command Finds Data for Nonexistent Field

Last reviewed: June 27, 1995
Article ID: Q115000
The information in this article applies to:
  • Microsoft FoxPro for Windows, versions 2.5, 2.5a, 2.5b, 2.6
  • Microsoft FoxPro for MS-DOS, versions 2.5, 2.5a, 2.5b, 2.6
  • Microsoft FoxPro for Macintosh, versions 2.5b, 2.5c

SYMPTOMS

The LOCATE command is used to search a table/.DBF for the first record that meets a given logical expression. However, if you perform a LOCATE FOR command on a field that does not exist in the selected database but a variable of the same name does exist, the LOCATE command will stop on the first record and FOUND() will return true (.T.).

For example, suppose you USE the CUSTOMER database (in the TUTORIAL subdirectory) in the current work area and issue the following commands in the Command window:

   m.notfield="A1000"
   LOCATE FOR NotField="A1000"

Although the field NOTFIELD does not exist, the LOCATE command will stop at the first record.

RESOLUTION

To avoid this problem, fully qualify the field name in the LOCATE FOR command; for example, LOCATE FOR customer.notfield="A1000". In the example above, this command will correctly return the error, "Variable NOTFIELD not found," meaning that the CUSTOMER.NOTFIELD field was not found.


Additional reference words: FoxMac FoxDos FoxWin 2.50b 2.60
KBCategory: kbprg kbprb
KBSubcategory: FxprgGeneral


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: June 27, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.