, , , ,

Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

run_report - heading length (OpenInsight 32-Bit)

At 18 APR 2006 02:46:29PM Karen Oland wrote:

I have a report with a very long header (see below) that works fine in AREV, but in OI (7.2.1) leaves a huge blank area at the top of the page. Short headers are working fine, but not this one – just testing a few, it appears that the longer the header is, the more extra blank lines are tossed at the top of the report (as if the formatting engine is allocating double the number of lines needed, when it is setting the margins).

Is there some built in limit on number of lines a header can contain before the large number of blank lines is added? Or can this bug be corrected in a future version?

The heading being used (this one and one with one line more than this one) for testing purposes (actual text changed from customer required text, but makes no difference in how it displays on page):

HEADING "'S25'report header'LDS1TS52'Page 'PPLL'first line of drivel'L'and the second'L' followed by more threats'L'and requiring me to sign below'L' that I am telling the truth.'L'"

At 18 APR 2006 03:35PM Gerald Lovel wrote:

You do not mention FONT and FONTSIZE specifications which might affect the calculated vertical spacing for the header.

At 19 APR 2006 08:27AM Bob Orsini wrote:

Karen, this is a bug and will be fixed in 8.0.

At 19 APR 2006 11:07AM Karen Oland wrote:

Thanks Bob. I could not see any control I had over the problem (since I am not passing any parameters to run_report other than the command).

At 19 APR 2006 02:12PM dsig _at_ sigafoos.org wrote:

cool man .. converting some PICK code the headers are almost a story in their own .. those guys knew how to use the system

so .. when is 8?

At 19 APR 2006 03:46PM Karen Oland wrote:

Bob,

Although easily worked around (for those that don't mind "fixing" several dozen reports and creating a non-conv routine to take it's place), another "bug" appears for anyone that took advantage of the ability to do a "blank" oconv (actually, using a space: OCONV " ") in a report - which left the data in a raw format. When run_report sees this, it goes nuts (it ignores most stuff after that, but not all, starts putting break-on control values in the columns instead of using them to break pages, skip lines etc).

It does appear (so far), that setting COLLENGTH 0 is working (with a blank colheading), but I haven't tested all of those reports yet (was useful for adding info into a header, but not displaying in the body of the report at all).

View this thread on the Works forum...