INF: SQLState 22002 Error When Fetching Results

 Last reviewed: January 8, 1997
Article ID: Q158618
The information in this article applies to:
  • Microsoft ODBC SDK, version 2.5
  • Microsoft ODBC SQL Server driver, versions 2.5 and 2.65

SUMMARY

While fetching results using ODBC SQL Server driver, you may occasionally see the following error message: 

   SQLState 22002: Indicator variable required but not supplied
This error message is not documented in either the SQL Server driver Help file or the ODBC 2.5 SDK specification document Readme25.txt that ships with the ODBC Desktop Driver Pack 3.0.

MORE INFORMATION

The problem is a documentation bug with the ODBC 2.5 SDK for the SQL State 22002 on SQLFetch. The SQL Server driver follows the ODBC SDK 2.5 specification and returns the error message correctly, as described in the specification.

According to the ODBC 2.5 specification, the driver should return error 22002 on SQLFetch when the data fetched in the particular column is NULL and the SQLBindCol function did not specify a valid pointer for the pcbValue parameter (indicator variable). This is because the driver returns SQL_NULL_DATA in the pcbValue parameter when the data fetched for a particular column is NULL. When the pcbValue is specified as a NULL pointer in your application, the driver raises the correct error message according to the specification.

NOTE: It is generally a good programming practice to specify valid pointers to the pcbValue parameter.

Additional reference words: 2.50 2.65 MFC VC++ 4.0
KBCategory: kbprg kberrmsg
KBSubcategory: SSrvProg SSrvGen

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