Re: No Oracle Client

I don't think you are correct. Here is part of their literature: "Oracle driver for dbExpress (DBExpOda) provides direct high performance access to Oracle database server. It can work using Oracle Call Interface (OCI) or SQL*Net directly. DBExpOda supports Oracle 7, Oracle 8, Oracle 8i and Oracle 9i. Driver requires Oracle software installed on client side to access through OCI. In case of working through SQL*Net TCP/IP protocol required only.
"
Sql net is the client software. OCI is a the Oracle call interface and on the windows platform it is a dll that uses the client software. You still need to install the client software. These in fact may be good drivers, but you still need the Oracle supplied piece. Jim
"John Young" <tj_yang_at_163.net> wrote in message news:e3feb707.0203120039.47723b6c_at_posting.google.com...
> try the things on www.crlab.com,
> they can connect to oracle database without the fat oracle client
 software!
>
> john Young
>
> "Jim Kennedy" <kennedy-family_at_attbi.com> wrote in message
 news:<bWej8.25896$uA5.28827_at_rwcrnsc51.ops.asp.att.net>...
> > Why not? The client alone isn't really very useful. I would ask
 Oracle,
> > but I would find it difficult to believe that they mind you installing
 the
> > Oracle client - they are licensing the database. Give them a call.
> > Jim
> > "Kuizad" <kuizad_at_yahoo.com> wrote in message
> > news:7f78ee91.0203102256.6c782993_at_posting.google.com...
> > > Dear Jim and all friends out ther
> > >
> > > thanks for the response and the knowledge shared.
> > >
> > > from all this i can make out that i have to use ODBC to connect and i
> > > will need the Oracle client. But i cannot distribute the Oracle Client
> > > with my application, unless i have necessary understanding with Oracle
> > > Corpn.
> > >
> > > anyways for the moment i close this discussion, however if anyone has
> > > any ideas we can always share them.
> > >
> > > thanks once again.
> > > kuizad
> > >
> > >
> > > "Jim Kennedy" <kennedy-family_at_attbi.com> wrote in message
 news:<Nsti8.12913$q2.1931_at_sccrnsc01>...
> > > > Let me dispel some myths about ODBC. All MS supplies with ODBC is a
 thin
> > > > layer to manage ODBC drivers. So when you want to use ODBC all you
 are
> > > > doing is calling the ODBC manager (MS) and asking it to load the
 ODBC
> > > > driver(the database vendor's driver). ODBC is just a specification
 on
 how
> > > > to call an ODBC driver (and the driver talks to the database in
 whatever
> > > > manner the database knows how to talk to native clients). So in
 Oracle's
> > > > case here is what happens.
> > > >
> > > > Let's say MS Access wants to issue a query to an Oracle database via
> > > > ODBC.(in a high level description)
> > > > Access calls the MS ODBC manager and asks to use the Oracle ODBC
 driver.
> > > > The MS ODBC manager loads the Oracle ODBC driver.
> > > > Access issues a command to the ODBC layer (eg select * from emp) for
 the
> > > > Oracle ODBC driver.
> > > > MS ODBC manager directs the call to the specified ODBC driver - in
 this
 case
> > > > Oracle's ODBC driver.
> > > > Oracle's ODBC driver translates what it got to its native API (in
 this
 case
> > > > OCI - Oracle call interface - their public interface)
> > > > Then the OCI calls talk to UPI - I think- which is Oracle's internal
> > > > interface and is not public.
> > > > These calls go out over sqlnet to the database that was specified in
 the
> > > > connection.
> > > >
> > > > So you see ODBC is just a high level api and not a method of how the
> > > > middleware works.
> > > > The concequence is that many people could write an ODBC driver that
 connects
> > > > to Oracle. In fact, Oracle does, MS does, Merant or Intersolve does
 just
> > > > that. But they all need the middle ware that Oracle does supply.
 Okay,
 I
> > > > did know of one company that did not need the Oracle middleware on
 the
> > > > client. Their drivers were very expensive. Why? You needed to
 install
> > > > their middleware. They had a process running on the Oracle server.
 It
 was
> > > > this process that used Oracle's middleware on the server. So they
 were
> > > > reproducing the functionality that Oracle shipped in the box. So
 from
 the
> > > > client to the server they had written their own type of sqlnet.
> > > >
> > > > So ODBC does not supply the middleware. It seems that way with MS
 because
> > > > the bundle in the OS installation the middleware for their database.
 So
 it
> > > > seems like you don't need to install middleware for MS Sqlserver,
 but it
 is
> > > > becasue it is already installed as part of installing a MS windows
 OS.
 I
> > > > don't think Oracle or IBM could convince MS to allow Windows to be
 shipped
> > > > with their middleware already installed as part of the OS.
> > > >
> > > > Jim
> > > >
> > > > "Johan Mårtensson" <johan7204_at_yahoo.com> wrote in message
> > > > news:a6bjs9$e8b$1_at_green.tninet.se...
> > > > > How about using ODBC?
> > > > >
> > > > >
> > > > > Jim Kennedy <kennedy-family_at_attbi.com> wrote in message
> > > > > news:%xAh8.13919$L7.19287_at_rwcrnsc52.ops.asp.att.net...
> > > > > > While 0040 is good it still needs all the rest of the stuff.
> > (tnsnames
> > etc.)
> > > > > > Jim
> > > > > > "Edwin" <vanmeerendonk_at_wxs.nl> wrote in message
> > > > > > news:31354201.0203060655.6bce9436_at_posting.google.com...
> > > > > > > I think with ado you can "just" install Oracle Objects for Ole
 (OO4O).
> > > > > >
> > > > > >
> > > > >
> > > > >
Received on Tue Mar 12 2002 - 15:31:46 CET