Re: 4GL Report problems on HP?!? Another Bug

One method to getting around this (if you IT Department wants to see a single BLANK page with header etc., even if there is no DATA) is to initiate a flag to FALSE before your START REPORT statement, in the FOREACH or FOR loop where you are generating data set the flag to TRUE Before the FINISH REPORT check the flag and if it is still FALSE perform an OUTPUT TO REPORT statement passing a NULL value (of course you will have to code for this in the REPORT section) and then perform the FINISH REPORT statement. Gives the bean counters what they want...proof the report ran. -- Rob Vorbroker Phone: 513/336-6741 Vorbroker Consulting FAX: 513/336-6742 www.vorbroker.com Daniel Wright <dw420@airmail.net> wrote in article <9F376D662BA4D779.8C0B40EF57A94305.0D8F6DE89A1961C4@library-proxy.airnews.ne t>... > Well, it must be another bug....strangely enough, if you remove the ORDER BY > in the REPORT, it works (but of course it's not in the right order), but hey > who cares. > > Strangely enough, this was not the same thing as the other report that > wouldn't print, which turned out not to be an Informix-HP port bug, but > rather an Informix-AIX bug....the bug was that it worked in AIX....According > to the 4GL Reference Manual, the PAGE HEADER is NOT processed until a print, > skip, or need statement is processed in the ON EVERY ROW, or BEFORE or AFTER > GROUP OF clauses. Therefore, without that, you shouldn't see the page > header, and in that case, that was exactly what was happening. > > Daniel Wright wrote: > > > I've known about a problem with using "START REPORT report_name" and > > trying to specify the filename in the REPORT function with "OUTPUT TO > > report_filename", for a while....it generally doesn't seem to work, at > > least with HP-UX (we're using 10.20) with Informix 7.xx (I've seen it on > > 7.14.???, as well as 7.21.UC1). It will work in the debugger and it > > will work if you use "START REPORT report_name TO report_filename". > > [Version of our 4GL is 6.04.UC3] > > > > BUT, I'm wondering if there are any other known problems with reports. > > > > After debugging a program (being more interested in the data it created > > than the reports), I decided to check the 3 reports that it generated, > > but it had stopped outputting anything to the reports (yes it had output > > before). I made sure it was still calling the START, OUTPUT, and FINISH > > report stuff (it was). I hadn't touched the variables it passed to the > > reports or the actual report calls, and even double-checked them > > anyway. Everything looked good, but still no output. > > > > I ran it thru the debugger, and got most of one report, none of another, > > and all of the 3rd, except the ORDER BY (used in the REPORT function, > > without an EXTERNAL, btw) was all screwed up. (It was neither in the > > order the rows were passed nor the desired order). > > > > I would have thought this was some subtle bug I introduced while > > debugging, BUT before I could solve it, I was called to the scene of > > another problem which seemed very similar...That program had been > > working fine on a number of AIX systems running Informix 5 (and quite > > probably also version 7), but failed to produce any reports on HP-UX > > (This was on 7.14.???, I can find out the version of the tools, if you > > think it matters).. > > > > Any help would be greatly appreciated. > > > > -- > > - Danny Wright > > danwright@nospam.com > > to reply by email, replace the "nospam" with "bigfoot". > > No headhunters please... > > #include <stddisclaimers.h> > > > > -- > - Danny Wright > danwright@bigfoot.com > #include <stddisclaimers.h> > > >