Platform: NT4.0, VisualC++ ODBC SDK 3.0, Oracle 2.5 ODBC driver (latest)
Problem:
When binding arrays of parameters a problem occurs on INSERT when the FIRST
element of the len/ind array specifies SQL_NULL_DATA. In this case ALL
elements of the corresponding value array are interpreted as NULL data.
For all other elements in the len/ind array the behaviour seems to be
correct and only affects the corresponding element in the value array.
I am using the binding of arrays of parameters successfully for datasets
that are guaranteed NOT NULL with speed improvements of a factor of 3(!!!)
in a client/server app. (with relatively small buffers, 10 or 12 elements)
For debugging purposes I have used both the ODBC 3.0 method of
SQLSetStmtAttr and the ODBC 2.0 SQLSetParamOptions. The problem occurs in
both cases.
Has anybody out there seen this?? Has anybody got an idea?? (constructive
ones only please...:-))
Please reply by e-mail as well since I am not a regular on these
news-groups
Thanks.
Erik
