Contents|Index|Previous|Next
SQLBindParam Mapping
SQLBindParam cannot truly be called deprecated because it was never there in ODBC;
However, it does still represent duplicated functionality, since the Driver Manager
needs to export it because ISO- and X/Open-compliant applications will be using
it. Because SQLBindParameter contains all the functionality of SQLBindParam, SQLBindParam will be mapped on top of SQLBindParameter (when the underlying driver is an ODBC 3.0 driver). An ODBC 3.0 driver does
not need to implement SQLBindParam.
When the following call to SQLBindParam is made:
SQLBindParam(StatementHandle, ParameterNumber, ValueType, ParameterType,
ColumnSize, DecimalDigits, ParameterValuePtr, StrLen_or_IndPtr)
the Driver Manager calls SQLBindParameter in the driver as follows:
SQLBindParameter(StatementHandle, ParameterNumber, SQL_PARAM_INPUT, ValueType,
ParameterType, ColumnSize, DecimalDigits, ParameterValuePtr, BufferLength,
StrLen_or_IndPtr)