Hi  !

I try to have some informations to optimize the communication between
an application developped under VB4(32) and an ORACLE 7.3 server.

We use the 32 bits ODBC provided by ORACLE.

Can anyone pls give me complements on this subject.

I have not used Oracle, but I know many people who have.  They all say
the same thing: Oracle is a wonderful product.  All you need is a
bottomless pit full of money to keep throwing at it, and you can do
anything you like.  

For example - want to build a new crosstab report - fine - just double
the size and performance of your server hardware first.

VB is NOT the problem here.

->Hi  !
->
->I try to have some informations to optimize the communication
between
->an application developped under VB4(32) and an ORACLE 7.3 server.
->
->We use the 32 bits ODBC provided by ORACLE.
->
->Can anyone pls give me complements on this subject.
->
->

Graham Daniell
Perth, Western Australia

  Hi  !

  I try to have some informations to optimize the communication
  between
  an application developped under VB4(32) and an ORACLE 7.3 server.

  We use the 32 bits ODBC provided by ORACLE.

  Can anyone pls give me complements on this subject.

 I am using the Openlink ODBC?data drivers. They work fine now, but I
was having massive speed problems. This was because I was sending
everything through the jet engine.

By using dbSQLPassThrough instead of the Jet engine, performance
increase is astronomical.

Regards
Dave Howell

I'm using the INTERSOLV Oracle ODBC drivers and have had no performance
problems, even going through the Jet, although using the ODBC API directly
is faster.

The ODBC driver provided by Oracle themselves is a waste of time. It is
very slow and doesn't support very much. In our test dbSQLPassThrough
queries took longer than going through the Jet (figure that one out!), and
multiple table updates were taking as long as 40 seconds !. We now have
sub second performance using INTERSOLV's ODBC driver.

Hope this helps.

Chris