We're currently in the process of upgrading from WebFocus 7.7.05 to 8.2.06. The table headers in our AHTML formatted reports are now being wrapped in a div with a fixed width. So, the html looks something like this:

- table id="ITableData0"
 - tr
  - td colspan="4" align="CENTER"
   - div style="width:64px;"
    - span ....TABHEADING text is here
  

In 7.7, that div was there but it had no specified width so the text could stretch across the entire top. Now it's confined to a tiny box (the main table itself is 550px wide) which makes the text wrap, pushing the content down the page and generally just looks ridiculous. The TABHEADING is styled like this:

TYPE=TABHEADING,
     LINE=2,
     SIZE=11,
     JUSTIFY=CENTER,
$

In a different report, the main table is 1803px and the heading div is 86px. I don't see any obvious relation between the two widths. I've tried looking through the json files in srv82\home\etc\ar_v1 (found by searching for irpcfg.js based on what I found in the the 8.0.10 docs, though it now seems to be irpcfg.json in 8.2.06) there's no obvious corresponding style.

Does anyone know if there's a way to turn this off or at least specify some saner width?

This message has been edited. Last edited by: FP Mod Chuck,

IMHO, since 8206 is pretty new you should open a case.

Have you tried setting AUTOFIT off on the table or SQUEEZE OFF on the report?

Either of those can cause things to force a set width on the table to the largest contents, if they are off you should not have that problem.

Neither AUTOFIT nor SQUEEZE settings seem to have an effect.

quote:

TYPE=TABHEADING,
LINE=2,
SIZE=11,
JUSTIFY=CENTER,
$

Try removing the LINE=2 part of your style. That will only format the second line of your report heading (SUBHEAD)

quote:

Originally posted by Hallway:
Try removing the LINE=2 part of your style. That will only format the second line of your report heading (SUBHEAD)

The styling doesn't seem to matter as far as that div goes. It's there even if I remove all of the styling.

quote:

IMHO, since 8206 is pretty new you should open a case.

As this is an upgrade issue (potentially) I agree with Martin, open a case with tech support.

T