Re: HELP!! Unable to parse query...

I've had similar problems with Unable to parse query.

We pass lexical parameters to our reports.

With Reports 2.5, we had to replace every occurrence of a single quote with two quotes in the parameters.

If all else fails, start pulling your report to bits trying to isolate the offending code.

Regards
Mal.

Angel Perez wrote:
>
> Michael Rosadino wrote:
> >
> > Has anyone run across the error "REP-0496: Unable to parse query" in
> > Reports 2.5.5.2.7? I have a character mode report which utilizes a
> > file-based SQL statement that contains an outer join, a 'NOT IN'
> > sub-query test in the WHERE clause and some optimization hints at the
> > top of the SELECT clause, e.g., /*+ USE_NL(...)*/, /*+ INDEX_ASC(...)*/.
> > Oracle tech support was not able to help me much and what's really
> > strange is that the same exact SQL statement runs fine in SQL*Plus 3.3.
> > The SQL statement ran fine before I added the sub-query and the
> > optimization hints but it still failed to execute successfully even
> > after I commented these additions out. Anyone who has had experience
> > with this, please respond.
> > Thanks,
> > --
> > Michael Rosadino
> > E-mail: mrosadino_at_connico.net
> > Gerber Garment Technology, Inc.
> > (860)871-8082, x3484
>
> Hi,
>
> We had a similar problem (with simpler SQL statements) when we had to
> connect to Oracle 7.3 Finally we discovered that wasn't the SQL wich
> gave the problem, but the SQL*Net connection which have been upgraded
> and re-upgraded over older files. We then cleaned up our PC's from
> Oracle Developer files and installed correctly the last versions we had
> (Forms 4.5.7.1.2 and Reports 2.5.5.2.5) and everything worked fine.
> Who said magic is lost? :)
>
> Hope this helps,
>
> Rafa Flores Yoldi
> cesinsl_at_redestb.es
  Received on Fri Jun 20 1997 - 00:00:00 CEST