Report crashes when using "order by"
Posted in 2000
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Server Administration
Hello, all,
I'm trying to solve a problem on a platform I am
not familiar with.
CPU: Alpha OSF1 V4.0
Informix: Dynamic Server 7.30.FC7
4GL 7.20.UD6
The situation is that when using an "order by"
clause in the OUTPUT section of a report, the
program segmentation faults.
I tried running dbx on the 4ge and I get a
stack backtrace of:
0 _iqcddcl() [iqcursor.c:469 ...]
1 gen_rpt(fgl_pcnt = 0, fgl_operation = 0)
2 main(fgl_argc = 1, fgl_argv = 0x...)
I looked at the C code and saw the SQL statements
that it would try to run. They worked fine
in dbaccess.
The fellow asking me to help him said that the
programs used to work fine. He said that if
he recompiles he sees this problem, but old 4ge's
work ok. I am not aware of anything that would
have changed with the Informix product recently.
I would appreciate any help anyone can provide.
Also appreciated would be messages sent via
email, instead of/in addition to this group.
Many thanks,
John
Sent via Deja.com http://www.deja.com/
Before you buy.
Does he have a matching ORDER BY clause in the SQL loop driving the
report? Does it match? Try moving the ORDER BY to the outer loop by
including it in the SELECT in the module calling the REPORT ,odule.
Then in the OUTPUT section of the report module make the ORDER BY
an ORDER BY .... EXTERNAL. If there is a bug in the report module
generated sort code this may work around it.
Art S. Kagel
jpletikapich@my-deja.com wrote:
>
> Hello, all,
>
> I'm trying to solve a problem on a platform I am
> not familiar with.
>
> CPU: Alpha OSF1 V4.0
> Informix: Dynamic Server 7.30.FC7
> 4GL 7.20.UD6
>
> The situation is that when using an "order by"
> clause in the OUTPUT section of a report, the
> program segmentation faults.
>
> I tried running dbx on the 4ge and I get a
> stack backtrace of:
> 0 _iqcddcl() [iqcursor.c:469 ...]
> 1 gen_rpt(fgl_pcnt = 0, fgl_operation = 0)
> 2 main(fgl_argc = 1, fgl_argv = 0x...)
>
> I looked at the C code and saw the SQL statements
> that it would try to run. They worked fine
> in dbaccess.
>
> The fellow asking me to help him said that the
> programs used to work fine. He said that if
> he recompiles he sees this problem, but old 4ge's
> work ok. I am not aware of anything that would
> have changed with the Informix product recently.
>
> I would appreciate any help anyone can provide.
> Also appreciated would be messages sent via
> email, instead of/in addition to this group.
>
> Many thanks,
> John
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.