ODBC and Crystal Reports 9 (OpenInsight 32-Bit)
At 30 APR 2004 04:51:25PM Peter Ashby wrote:
There are some patches out on the Crystal site that fix the sql syntax problem with quotes. These are cr90mainwin_en, cr90dbexwin_en and cr90devwin_en. All are zip files.
Main updates various items in Crystal itself, the dbex is for database connections and exports and the devwin file is additional developer edition fixes.
After installation there is a new registry entry string for 'NoQuotes'-
HKEY_LOCAL_MACHINE\SOFTWARE\Crystal Decisions\9.0\Crystal Reports\Databases\QueryBuilder\NameBuilder
Put in the path to revdobc.dll and things revert back to 8.5 days - no need to enter the sql command manually, and it seems to be a little faster as well.
I hope this helps those that are having some problems with Crystal and the ODBC driver.
At 30 APR 2004 05:30PM Jim Vaughan wrote:
Where on the Crystal site can you download these files?
Has anyone tried version 10?
At 01 MAY 2004 09:03AM Mike Ruane wrote:
Pete-
Thanks very much for the info.
See you in NOLA?
Mike
At 01 MAY 2004 09:51AM Peter Ashby wrote:
www.businessobjects.com - service, support crystal technical support, download monthly hot fixes, crystal reports - you should be able to see the files listed there for download.
Hope that helps.
At 01 MAY 2004 05:55PM Peter Ashby wrote:
A new wrinkle with Crystal building the sql statement - if the where clause includes a date field, sql builds the statment as follows:
… FROM EMP_ACTIVITY EMP_ACTIVITY
WHERE EMP_ACTIVITY.ACT_DATE]={d '2004-01-01'}…
The ODBC driver does not seem to understand the date format, returns error returning rowset and then a sql syntax error.
We can work around by running the date select after the initial data load and not refresh the data when requested.
At 02 MAY 2004 05:12PM Jim Vaughan wrote:
I can not access the www.businessobjects.com web page.
At 03 MAY 2004 08:46AM Peter Ashby wrote:
Their site appeated to be down yesterday evening, but it is up again now - I just tried it (8:45am)
At 03 MAY 2004 01:40PM Jim Vaughan wrote:
]] After installation there is a new registry entry string for 'NoQuotes'-
HKEY_LOCAL_MACHINE\SOFTWARE\Crystal Decisions\9.0\Crystal Reports\Databases\QueryBuilder\NameBuilder ] Put in the path to revdobc.dll and things revert back to 8.5 days - no need to enter the sql command manually, and it seems to be a little faster as well. «
I am unsure what this means, I don't seem to have a revdobc.dll file.
At 03 MAY 2004 01:54PM Peter Ashby wrote:
for the new NoQuotes registry entry enter the full path - mine is
c:\winnt\system32\revodbc.dll
This should be where your Revelation ODBC driver is installed. If not, point it to where you installed it.
At 03 MAY 2004 02:09PM Jim Vaughan wrote:
Ah OK, let me give that a try.
Thanks.
At 03 MAY 2004 02:28PM Jim Vaughan wrote:
At 03 MAY 2004 02:29PM Jim Vaughan wrote:
With these changes I still get the "Failed to open a rowset error".
However I am running with a patch from Sean.
I'll keep you updated on any progress.
At 03 MAY 2004 04:24PM Peter Ashby wrote:
What does the sql command look like - Database - Show SQL Query
That should tell what the problem is - could be a date if you are selecting on a date. I have posted a question on the Crystal site about this.
If you let Crystal select the entire dataset then use the selection expert to refine it after that point. Do not refresh the data after the initial selection. Also seems to work better if you do not 'perform select on server'.
At 03 MAY 2004 05:15PM Jim Vaughan wrote:
SELECT WORK_ORDER.ID, WORK_ORDER.DESC FROM W_TACTIC.WORK_ORDER WORK_ORDER
At 03 MAY 2004 06:58PM Jim Vaughan wrote:
I also had problems with "could be a date if you are selecting on a date". This was fixed in one the patches that Mike sent me. If it's not working then maybe the patch never made it into the current version of OI.
At 04 MAY 2004 08:18AM Sean FitzSimons wrote:
Jim,
All the patches you have, except the one sent by me the other day, are in the product.
Sean
At 04 MAY 2004 02:39PM Jim Vaughan wrote:
Prior to the latest release of OI, Mike had sent me patches that allowed the ODBC driver to work with Crystal.
These patches corrected at least two problems:
(1) Quotes and maybe other formatting issues.
(2) Date fields not working. To be exact the code crashed if the date was non integer.
So either the current version created new (but similar problems) or something did not make into the current version.