ODBC SetSQLConnectAttr() order
From: Guy Rouillier <guyr_at_raleigh.ibm.com>
Date: 1998/02/26
Message-ID: <6d4os9$1teg$1_at_rtpnews.raleigh.ibm.com>#1/1
Date: 1998/02/26
Message-ID: <6d4os9$1teg$1_at_rtpnews.raleigh.ibm.com>#1/1
I have some working ODBC code that I'm using to model my new Oracle
ODBC application. I use the following two statements to turn off
AUTOCOMMIT:
SQLSetConnectAttr()
SQLConnect()
When I execute these two statements with an Oracle datasource, I get the following error:
iRC: 1 SQL Code: 0 State: IM006 Message: [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
However, if I reverse the order of the calls, everything works. Oracle seems to be misbehaving in this regard. Should Oracle be able to accept the original order? Received on Thu Feb 26 1998 - 00:00:00 CET