Re: Problem with apllication developped whith ODBC 2.x running whith ODBC driver version 3.0.

Hi,
You should check out OpenLink's drivers; we do not have this problem. They're available for free non-expiry evaluation from http://www.openlinksw.co.uk/ onwards.

Regards,

~Tim

In article <6vaeta$4d$1_at_jaydee.iway.fr>,   "Florian RIVAL" <t-data_at_alpes-net.fr> wrote:
> Hi,
>
> Does anybody knows some problems whith application developped with ODBC
> version 2.x and running with ODBC driver version 3.0.
>
> Personnaly, in this context, an error often appears : "Driver's
> SQLSetConnectAttr failed" (error code IM006), this function is equivalent to
> SQLSetConnectOption in version 2.x. I think it's a bug of the translation
> table between the version 2.x and 3.0 because this error appears when the
> application is executing an 'SQLExecDirect' instead of an
> 'SQLSetConnectOption'.
>
> Another problem is that, regularly, the application not responding when
> executing an SQLExecDirect for insert or for update and, I must kill the
> process and restart the application to solve this problem; the execution is
> stopped in ODBC functions.
>
> These two problems seems to be only one.
>
> If someone have an explaination (and may be a solution), please answer me.
>
> Rem. : The application is running whith ORACLE drivers version 3.0
> (Intersolv) on UNIX
> system.
>
> Thanks,
>
> Florian RIVAL.
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Fri Oct 09 1998 - 00:00:00 CDT