Why use ODBC! It only supports bind variables as string substitutions and
thus causes a lot of parses. I would be tempted to use native API calls.
Worked at a place where the DB driver engineer could churn out a fully
functional driver (fully tested etc. ) in 30 days (from when he got the
manuals and a sample database up and had basic connectivity etc.) or less.
Always found native drivers more efficient than ODBC.
Jim
"Andy Hallam" <ahm_at_exel.co.uk> wrote in message
news:9jm0ts$n2f$1_at_reader-00.news.insnet.cw.net...
> Oracle 8i DOES NOT support binding of UNICODE strings through ODBC on
INPUT
> parameters. It does support UNICODE strings on OUTPUT though, I think that
> is what you mean.
>
> For example,
> SQLBindParameter for a unicode string on input (SQL_PARAM_INPUT) will not
> work. (i.e INSERT SQL)
> SQLBindCol for a unicode string on output will work. (i.e SELECT SQL)
>
> Luckily though ORACLE says it will support this in 9i...
>
> Andy.
>
> "Justin Cave" <jocave_at_yahoo.com> wrote in message
> news:233b7a65.0107240610.2e614f3b_at_posting.google.com...
> > "Andy Hallam" <ahm_at_exel.co.uk> wrote in message
news:<9jjcdk$38l$1_at_reader-00.news.insnet.cw.net>...
> > > I am currently porting our C++ applications from INFORMIX & SQL SERVER
to
> > > ORACLE.
> > >
> > > Besides countless other 'bodges' I have had to get round for ORACLE
(like
> > > cannot even bind a UNICODE string as an input parameter through the
ORACLE
> > > ODBC driver)
> >
> > Note that unless you're using a really antiquated version of the
> > Oracle ODBC driver, you certainly are able to bind a UNICODE string.
> > You can download updated versions of the driver from
> > <http://otn.oracle.com> if you're currently using an outdated version.
> >
> > Justin Cave
>
>
Received on Wed Jul 25 2001 - 21:30:34 CDT
