Xref: alice comp.databases.oracle.server:59606 comp.databases.oracle.tools:29253 Path: alice!news-feed.fnsi.net!newsfeed.icl.net!colt.net!dispose.news.demon.net!demon!bullseye.news.demon.net!demon!news.demon.nl!demon!sybrandb.demon.nl!not-for-mail From: "Sybrand Bakker" Newsgroups: comp.databases.oracle.server,comp.databases.oracle.tools Subject: Re: C++ to Oracle Server Date: Thu, 29 Jul 1999 20:58:18 +0200 Message-ID: <933274690.26334.0.pluto.d4ee154e@news.demon.nl> References: <379FEFB7.F06F03C9@vsl.com.au> Reply-To: "Sybrand Bakker" X-Trace: news.demon.nl 933274690 pluto:26334 NO-IDENT sybrandb.demon.nl:212.238.21.78 X-Complaints-To: abuse@demon.net X-Newsreader: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Lines: 30 Hi Steven, With Oracle products you have three options: (from low level to high level) 1 OCI (Oracle Call Interface). The OCI itself has been written in C. Here you can and you must do everything yourself, compare it with using system calls. 2 Pro*C. This is essentially a pre-compiler, it translates your calls of Pro*C routines to ordinary C. You have both static and dynamic sql. Using it is far less difficult than OCI, and you still have flexibility. You can use Pro*C calls everywhere, also in your own functions/modules. 3 Oracle Objects for OLE. This is a VB/Access like interface to Oracle, though it doesn't use ODBC. You can have recordsets and all the like. Hth, Sybrand Bakker, Oracle DBA Steven Salvemini wrote in message news:379FEFB7.F06F03C9@vsl.com.au... > Does anyone have some experience with "talking" to oracle 8.0.5 or 8i > using MS Visual C++. > > If it must be done via Pro C, will C++ modules be able to talk to Pro C, > ie in terms of passing parameters, lists, arrays etc back and forth? > > >