Hello.
Please excuse me my English, i'm not native English speaker
I'm writing the ODBC driver for new DBMS
i've got stuck with following thing:
When client application calls SQLDescribeCol function
(supplying valid statement handle as a parameter)
driver manager doesn't redirect this call to my driver
all other functions are called normally.
When client application calls SQlDescribeCol
I see log entries in trace file that are containing
2 nested calls of SQLDescribeCol.
One (outer) with a valid statement handle and one
(inner)with handle that never appears in that log before.
inner one returns SQl_INVALID_HANDLE.
both of them are _NOT_ functions from my driver.
I've checked with debugger - SQLDescribeCol in driver is not called.
What this strange behaviour could be related with?
Please excuse me my English, i'm not native English speaker
I'm writing the ODBC driver for new DBMS
i've got stuck with following thing:
When client application calls SQLDescribeCol function
(supplying valid statement handle as a parameter)
driver manager doesn't redirect this call to my driver
all other functions are called normally.
When client application calls SQlDescribeCol
I see log entries in trace file that are containing
2 nested calls of SQLDescribeCol.
One (outer) with a valid statement handle and one
(inner)with handle that never appears in that log before.
inner one returns SQl_INVALID_HANDLE.
both of them are _NOT_ functions from my driver.
I've checked with debugger - SQLDescribeCol in driver is not called.
What this strange behaviour could be related with?