Field Names with Illegal Characters Cause Errors

Last reviewed: June 27, 1995
Article ID: Q117407
The information in this article applies to:
  • Microsoft FoxPro for Windows, versions 2.5x, 2.6
  • Microsoft FoxPro for MS-DOS, versions 2.0, 2.5x, 2.6

SUMMARY

Some database products allow field names to contain characters that are not allowed in FoxPro. An imported database containing those characters within the field names may cause certain FoxPro commands to report error messages such as "Syntax Error" or "Unrecognized phrase/keyword in command."

MORE INFORMATION

Both the MS-DOS and Windows versions of FoxPro stipulate that field names must begin with a letter A through Z. The field names can contain numbers or the underscore (_) character. However, many other software products allow field names to begin with or contain a variety of characters forbidden in FoxPro. Normally, opening these tables causes no problem.

However, some FoxPro commands, such as APPEND FROM, COPY TO, and COPY STRUCTURE TO, may generate errors if they encounter a field that contains an unrecognized character. These commands may also cause unpredictable results with fields that contain an unrecognized character.

For example, if a database field name contains a period (.) and the COPY TO <filename> command is executed from the Command window, the error message "Unrecognized phrase/keyword in command" appears.


Additional reference words: FoxDos FoxWin 2.00 2.50 2.50a 2.50b 2.60 dbf
errmsg
err msg
export convert translate migrate illegal invalid
KBCategory: kbprg kberrmsg
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.