Re: Oracle + ODBC Outer Joins + Drivers

No, the {OJ } syntax is correct for ODBC (this is the Outer Join escape clause) and is intended to remove db dependant syntax. I suspect that this is a limitation with the driver being used rather than the database. Why use the 3rd party driver for Oracle? If you really must use a 3rd party driver, try the ones from Intersolv (or whomever they have morphed into these days) or perhaps the ones from OpenLink.

"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message news:8q54mo$8fc$1_at_soap.pipex.net...
> "Charles Gamble" <Charles.Gamble_at_Singularity.co.uk> wrote in message
> news:ATIv5.17857$8r4.176965_at_news2-win.server.ntlworld.com...
> > Hi all,
> >
> > I am having a problem when using the ODBC {oj} Outer Join escape
 sequence
> > with Oracle ODBC drivers. When I use the current Oracle ODBC driver from
> > Oracle everything works fine. However, when I use the current Microsoft
> > Oracle ODBC driver I get problems when doing outer joins with more than
 one
> > table. (I am doing the JOINs using primary key fields).
>
> Hi I'm not sure if this is exactly the case but your queries would
 probably
> be better rewritten using the (+) operator. This would be the Oracle
> standard way of doing an outer join.
>
> regards & HTH
>
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
>
>
Received on Mon Sep 18 2000 - 19:11:44 CDT