FIX: SQL INSERT Error Does Not Report Errant Field Name

Last reviewed: September 22, 1997
Article ID: Q88967

2.00 MS-DOS kbprg kbfixlist kbbuglist

The information in this article applies to:

Microsoft FoxPro for MS-DOS, version 2.0

SYMPTOMS

When an incorrect field name is specified in the SQL INSERT command, the error message does not include the name of the incorrect field.

STATUS

Microsoft has confirmed this to be a problem in Microsoft FoxPro version 2.0 for MS-DOS releases dated prior to November 15, 1991. This problem was corrected in the Microsoft FoxPro version 2.0 for MS-DOS release dated November 15, 1991.

MORE INFORMATION

For example, in the following code, "pno" is not the name of a field in the database:

   INSERT INTO parts (pno, descript, onhand, onorder,price,cost);
      VALUES ('B6722','Royal Reindeer',2,6,27.99,20.65)

The resulting error message does not report "pno" as the errant field name.

Additional reference words: FoxDos buglist2.00 fixlist2.00 INSERT-SQL 2.00
KBCategory: kbprg kbfixlist kbbuglist
KBSubcategory:
Solution Type : kbfix

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: September 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.