Merant 3.5 or Crystal 8

The following fix Ted gave me seems to be the one that works. But I have
only tried it on one report. I'll keep my fingers crossed.

Rhonda Reilly

-----Original Message-----
From: Troy Funte [mailto:tfunte@...]
Sent: Wednesday, January 17, 2001 11:56 PM
To: vantage@egroups.com
Subject: Re: [Vantage] Merant 3.5 or Crystal 8


In my case, Seagate had to customize the registry fix for our installation.
I don't know why. It didn't work until one line was changed according to
the driver that was in use when running the report.

Troy Funte
Liberty Electronics


----- Original Message -----
From: Ted Kitch
To: 'vantage@egroups.com'
Sent: Wednesday, January 17, 2001 7:48 AM
Subject: RE: [Vantage] Merant 3.5 or Crystal 8


I just uploaded a file to eGroups called ivpro14 for 3.5.reg. Download
this
file and it will get rid of the "Unable to understand after DECLARE"
error.
This will need to be run on every machine that has Crystal Reports
installed
on it. You don't need to use it on machines that will just run the
reports.

The error message comes from the way that Crystal formats the SQL
statements
that are passed off to the ODBC driver. This registry file updates the
way
that Crystal formats the SQL statements.

Ted Kitch
tedkitch@...

-----Original Message-----
From: Reilly, Rhonda [mailto:rreilly@...]
Sent: Wednesday, January 17, 2001 8:34 AM
To: vantage@egroups.com
Subject: [Vantage] Merant 3.5 or Crystal 8

I upgraded my Crystal reports and the Merant ODBC Driver almost
simultaneously so I can't tell which is causing the problem. I am now
getting the Odbc error "unable to understand after "DECLARE" and have read
from past emails that you can take out the "(" and it will work. Yes that
is true but as I am building my reports (adding tables, joins, filters,
ect)
I am having to go back to the SQL statement hit the reset button and then
take the "(" out again. Is that what I am supposed to do or is there
another way around this problem.

Also thanks to all that answered my question about compiling reports in CR
8.

Thank you
Rhonda




eGroups Sponsor



<http://rd.yahoo.com/M=169066.1281467.2883016.2/D=egroupmail/S=1700007183:N/

A=560436/*http://cgi.timeinc.net/cgi-bin/magsubs/cc/subs/ecompanynowcc1?EFFO
RTKEY=ECABC84> Click Here!

To unsubscribe from this group, send an email to:
vantage-unsubscribe@egroups.com




[Non-text portions of this message have been removed]


eGroups Sponsor


To unsubscribe from this group, send an email to:
vantage-unsubscribe@egroups.com





[Non-text portions of this message have been removed]


To unsubscribe from this group, send an email to:
vantage-unsubscribe@egroups.com
I upgraded my Crystal reports and the Merant ODBC Driver almost
simultaneously so I can't tell which is causing the problem. I am now
getting the Odbc error "unable to understand after "DECLARE" and have read
from past emails that you can take out the "(" and it will work. Yes that
is true but as I am building my reports (adding tables, joins, filters, ect)
I am having to go back to the SQL statement hit the reset button and then
take the "(" out again. Is that what I am supposed to do or is there
another way around this problem.

Also thanks to all that answered my question about compiling reports in CR
8.

Thank you
Rhonda
I think Seagate could best help you on this.

Crystal has a hard time with some complex joins that Report Builder can handle fine. I have had to resort to using Subreports numbers of times when a normal "two-jointed" join (as I call them) needs to used. Crystal works best using straight table to table to table joins, and using a left-outer only at the last join (if a left outer is needed). If you need to divert a join from a straight line, I have found (after painfully 're-re-redesigning' a report that locked up) that a subreport is the least painful way. The drawback is in passing variables(difficult, but not impossible), and the incredible slowness that a subreport adds to processing time. But for some complex things that RB can't do, this is the only way.

Seagate has given me a registry fix program in the past that has helped me past a few errors, like the one you are describing. So do call them. The long distance charge has usually been worth it to me.

Troy Funte
Liberty Electronics

----- Original Message -----
From: Reilly, Rhonda
To: vantage@egroups.com
Sent: Wednesday, January 17, 2001 6:33 AM
Subject: [Vantage] Merant 3.5 or Crystal 8


I upgraded my Crystal reports and the Merant ODBC Driver almost
simultaneously so I can't tell which is causing the problem. I am now
getting the Odbc error "unable to understand after "DECLARE" and have read
from past emails that you can take out the "(" and it will work. Yes that
is true but as I am building my reports (adding tables, joins, filters, ect)
I am having to go back to the SQL statement hit the reset button and then
take the "(" out again. Is that what I am supposed to do or is there
another way around this problem.

Also thanks to all that answered my question about compiling reports in CR
8.

Thank you
Rhonda

eGroups Sponsor


To unsubscribe from this group, send an email to:
vantage-unsubscribe@egroups.com





[Non-text portions of this message have been removed]
I just uploaded a file to eGroups called ivpro14 for 3.5.reg. Download this
file and it will get rid of the "Unable to understand after DECLARE" error.
This will need to be run on every machine that has Crystal Reports installed
on it. You don't need to use it on machines that will just run the reports.

The error message comes from the way that Crystal formats the SQL statements
that are passed off to the ODBC driver. This registry file updates the way
that Crystal formats the SQL statements.

Ted Kitch
tedkitch@...

-----Original Message-----
From: Reilly, Rhonda [mailto:rreilly@...]
Sent: Wednesday, January 17, 2001 8:34 AM
To: vantage@egroups.com
Subject: [Vantage] Merant 3.5 or Crystal 8

I upgraded my Crystal reports and the Merant ODBC Driver almost
simultaneously so I can't tell which is causing the problem. I am now
getting the Odbc error "unable to understand after "DECLARE" and have read
from past emails that you can take out the "(" and it will work. Yes that
is true but as I am building my reports (adding tables, joins, filters, ect)
I am having to go back to the SQL statement hit the reset button and then
take the "(" out again. Is that what I am supposed to do or is there
another way around this problem.

Also thanks to all that answered my question about compiling reports in CR
8.

Thank you
Rhonda




eGroups Sponsor


<http://rd.yahoo.com/M=169066.1281467.2883016.2/D=egroupmail/S=1700007183:N/
A=560436/*http://cgi.timeinc.net/cgi-bin/magsubs/cc/subs/ecompanynowcc1?EFFO
RTKEY=ECABC84> Click Here!

To unsubscribe from this group, send an email to:
vantage-unsubscribe@egroups.com




[Non-text portions of this message have been removed]
In my case, Seagate had to customize the registry fix for our installation. I don't know why. It didn't work until one line was changed according to the driver that was in use when running the report.

Troy Funte
Liberty Electronics


----- Original Message -----
From: Ted Kitch
To: 'vantage@egroups.com'
Sent: Wednesday, January 17, 2001 7:48 AM
Subject: RE: [Vantage] Merant 3.5 or Crystal 8


I just uploaded a file to eGroups called ivpro14 for 3.5.reg. Download this
file and it will get rid of the "Unable to understand after DECLARE" error.
This will need to be run on every machine that has Crystal Reports installed
on it. You don't need to use it on machines that will just run the reports.

The error message comes from the way that Crystal formats the SQL statements
that are passed off to the ODBC driver. This registry file updates the way
that Crystal formats the SQL statements.

Ted Kitch
tedkitch@...

-----Original Message-----
From: Reilly, Rhonda [mailto:rreilly@...]
Sent: Wednesday, January 17, 2001 8:34 AM
To: vantage@egroups.com
Subject: [Vantage] Merant 3.5 or Crystal 8

I upgraded my Crystal reports and the Merant ODBC Driver almost
simultaneously so I can't tell which is causing the problem. I am now
getting the Odbc error "unable to understand after "DECLARE" and have read
from past emails that you can take out the "(" and it will work. Yes that
is true but as I am building my reports (adding tables, joins, filters, ect)
I am having to go back to the SQL statement hit the reset button and then
take the "(" out again. Is that what I am supposed to do or is there
another way around this problem.

Also thanks to all that answered my question about compiling reports in CR
8.

Thank you
Rhonda




eGroups Sponsor


<http://rd.yahoo.com/M=169066.1281467.2883016.2/D=egroupmail/S=1700007183:N/
A=560436/*http://cgi.timeinc.net/cgi-bin/magsubs/cc/subs/ecompanynowcc1?EFFO
RTKEY=ECABC84> Click Here!

To unsubscribe from this group, send an email to:
vantage-unsubscribe@egroups.com




[Non-text portions of this message have been removed]


eGroups Sponsor


To unsubscribe from this group, send an email to:
vantage-unsubscribe@egroups.com





[Non-text portions of this message have been removed]
Rhonda,

yes, you are correct in that you will have to keep an eye on the SQL query
as you add tables.

Also note that there comes a point in constructing a report where crystal
doesn't even seem to add the tables anymore - I recently wrote a report
using 8 or 9 tables, and after about 5 were added, even when I'd done my
visual linking for all 9 tables, Crystal hadn't added them to the query.

I had to copy the query out of Crystal and into Word, get a screen print of
my visual linking and manually finish off the query before copying it back
into Crystal.

It seems to take exception to the user editing it's query, and gives up.

I hope if you come across that, you've saved this e-mail, 'cos it'll save
some hair-tearing! (trust me, I'm bald....)


Anton Wilson,
Systems Analyst,
Deanestor Healthcare




------------------------------------------------
Message: 11
Date: Wed, 17 Jan 2001 08:33:58 -0600
From: "Reilly, Rhonda" <rreilly@...>
Subject: Merant 3.5 or Crystal 8

I upgraded my Crystal reports and the Merant ODBC Driver almost
simultaneously so I can't tell which is causing the problem. I am now
getting the Odbc error "unable to understand after "DECLARE" and have read
from past emails that you can take out the "(" and it will work. Yes that
is true but as I am building my reports (adding tables, joins, filters, ect)
I am having to go back to the SQL statement hit the reset button and then
take the "(" out again. Is that what I am supposed to do or is there
another way around this problem.

Also thanks to all that answered my question about compiling reports in CR
8.

Thank you
Rhonda
------------------------------------------------