ODBC / Native Driver Conflict 
Author Message
 ODBC / Native Driver Conflict
I have a PowerBuilder client application that uses a native driver to access
an Oracle 8 DB.
I modified the application so it would call a function in a DLL... call it
function X. Function X uses ODBC to access the same Oracle 8 DB.

The problem:
The application calls the function and the function executes successfully,
but the next time the application tries to access the database it crashes.
Using the ODBC connection screws up the native driver connection.

Has anybody seen this problem? What's the solution?



Wed, 18 Jun 1902 08:00:00 GMT
 ODBC / Native Driver Conflict

Sounds like a problem that I recently had with dynamic executions not
refreshing and allowing subsequent executions.  I had a similar bad behavior
where it blew up.  I want to here the answers to this one ...



Wed, 18 Jun 1902 08:00:00 GMT
 ODBC / Native Driver Conflict
I had this problem and reported it to Sybase. They confirmed it as a bug but
suggested the workaround was the best they could do. The workaround is to close
the ODBC connection before opening the native driver connection and vice versa.
Quote:

> I have a PowerBuilder client application that uses a native driver to access
> an Oracle 8 DB.
> I modified the application so it would call a function in a DLL... call it
> function X. Function X uses ODBC to access the same Oracle 8 DB.

> The problem:
> The application calls the function and the function executes successfully,
> but the next time the application tries to access the database it crashes.
> Using the ODBC connection screws up the native driver connection.

> Has anybody seen this problem? What's the solution?



Wed, 18 Jun 1902 08:00:00 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. Delphi, 16bit Native SQL-Server 6.5 native/ ODBC drivers

2. ntwdblib.dll vs sqlsrv32.dll (native driver vs ODBC driver)

3. SQL Server Native Drivers vs. ODBC Drivers

4. Why to use native driver for SQL instead of ODBC driver

5. ODBC driver installation conflicts (between 16 bit and 32 bit drivers) on NT

6. ODBC driver installation conflicts (between 16 bit and 32 bit drivers) on NT

7. native odbc drivers vs odbc

8. ODBC: state 37000 /native SQL Server 6.0 701/MS 32 Bit ODBC Driver

9. Warning State: S1T00,Native:0, Origin: [Microsoft][ODBC SQL Server Driver] timeout expired

10. ntwdblib.dll (Native vs. ODBC driver)

11. Using native SQL Server driver vs. ODBC

12. JDBC error while ODBC/native driver ok


 
Powered by phpBB® Forum Software