Hi Paul,

> > What about replacing the 5.6 driver with the open-source
> > (Jim's/IBPhoenix/Whatever it's officially called) one? The
> main problem
> > I see with it is that it doesn't work with Crystal--which
> tons of people
> > use for reporting.
>
> We have had a report from someone who said they got the IBP
> ODBC driver
> working on Crystal Reports 8. I've approached Crystal to see
> if they can
> send me an eval so that I can establish and document what is required.
> When I have more info I'll post it here.
>
> This is the trick to make it work (watch the wrap)
>
> HKEY_CURRENT_USER \ Software \ Seagate Software \ Crystal Reports \
> Database Options \ Outer Join \OpenIngres
>
> value: "odbcjdbc"
>
>
> As I say, this is just a single feedback report and we have not yet
> corroborated it. Neither do we know if this trick works with previous
> versions.

I can confirm that, but it's just Crystal's problem with ODBC - it supports
different outer join syntaxes and some ODBC drivers are defaulted to the
wrong group of syntax. Since you've changed this registry entry, all should
work fine. The same trick had to be done with Crystal 7 and Intersolv ODBC
driver as well.

And in my case there's only one problem with Jim's driver. As far as I can
understand, Crystal recognizes dialect 3 TIMESTAMP columns as STRING ones
with this driver and regularly crashes trying to retrive the values of those
columns. I don't know whether anyone else has encountered something similar,
but it would be great to fix this thing if such a bug really exists.

Excluding the above, I have it working with Crystal 8.

Cheers,
Dmitry