From: Paul R. <pr...@ib...> - 2002-06-10 16:26:36
|
Pier Alberto GUIDOTTI wrote: > I'm testing the latest changes with Crystal Reports 8.5. > I've seen a strange behaviour when using OUTER JOINS. > With previous version of the driver, OUTER JOINS were treated in the right > way by adding the following key in the registry: > > HKEY_CURRENT_USER\Software\Seagate Software\Crystal > Reports\DatabaseOptions\OuterJoin = 'odbcjdbc'. > > I downloaded the latest changes from CVS tree and recompiled them. Then I > tested the driver with Crystal. > Now OUTER JOINS are treated in a bad way, like this: > > SELECT > PERSON1.CODICE, PERSON1.NOME, > ENTI1.CODICE, ENTI1.DESCRIZION > FROM > { oj PERSON PERSON1 LEFT OUTER JOIN ENTI ENTI1 ON > PERSON1.ENTE = ENTI1.CODICE} > > The Oj operator is added to the query. It seems the registry key is ignored > by Crystal with the new version of driver, but why? > It may be due to the confusion of the string to use to describe the driver. In some places it is 'OdbcJdbc'. In other places it is 'Firebird/InterBase(r) driver'. I think we should be using the latter throughout. Try changing the registry entry and let us lnow if it works. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |