First the kudos -
Oterro is the most stable and reliable R:Base ODBC driver we've ever had.
Many of the problems we had in the past with the earlier R:Base ODBC
drivers (no support for views or computed columns, frequent ODBC errors,
and crashes back to the desktop, etc.) are history.
We can even use the "Use Server or indexes" feature of Crystal Reports for
"most" functions. Wherever this is supported, the R:Base ODBC driver
actually runs the queries instead of the Crystal Reports engine. This makes
for Crystal Reports based on R:Base databases to run 10 x faster than with
the earlier R:Base ODBC drivers, and sometimes it seems that they finish
running even before they started! This is truly a tremendous improvement :
-)
But there is one type of query that doesn't allow us to use "Use Server or
indexes" - a query based on a date data type.
I've reported this to RBTI, but have been told it's because the Crystal
Reports query engine inserts "garbage" into the query whenever it's based
on a date. The tech support folks at Crystal Reports deny that and state
that they pass the same query that is passed for any other data type except
to designate it "d" as a date data type.
I'd like to know if anyone else has run into this and if they were able to
get it to run.
BTW, if you go to the SQL Syntax of Crystal Reports and manually change it
to conform to R:Base syntax (true SQL) it works.
In addition,the Crystal report will run, very slowly, if "Use Server or
indexes" is not selected.
You might wonder why I am trying to use Crystal Reports when the R:Base
report engine is available. I've provided Crystal Reports to my customers
so that they can create and run ad hoc reports without having to go to the
R:. I only provide them access to the R:Base databases via applications
I've provided via RTW 6.5+
Thanks for your time.
Tony
Anthony Schmidt
President
The Computery Ltd.
One East Main Street
Bay Shore, NY 11706
Voice 631-665-8100
Fax 631-969-5988
