Dale, You might want to, at least temporarily, downgrade to 0.43, which will mean that you should build it from the source.
Unfortunately, there were a number of code changes that went along with moving to 3.x for correctness, so I'd be surprised if it worked as a 2.x app anymore, but if you build from the source, you may be able to take out the SQLSetEnvAttr in the connect function. Jeff > -----Original Message----- > From: Dale Durham [mailto:[EMAIL PROTECTED] > Sent: Friday, March 07, 2003 2:27 PM > To: '[EMAIL PROTECTED]' > Subject: SQLSTATE ($h->state) mappings > > > Is anyone working on (or is there a way to tell) the driver > to pass ODBC 2.x state returns instead of 3.x (given the > current DBD::ODBC driver is a 3.x 'app')? I have thousands of > testcase that verify the $h->state() along with other returns > such as $h->err. Once I upgraded to newer DBI and DBD::ODBC I > now get ODBC 3.x state returns. Through ODBC, I can pass > SQLSetEnvAttr to tell the driver to return ODBC 2.x states. > How can I deal with this via DBI since DBD::ODBC does not > have a function for this? > > Regards, > Dale >
