Repeating Group Headings w/Columns 6

[JLZ99]

Has anyone successfully gotten the Group Heading to repeat at the top of subsequent columns after the first, while using the 'multiple column' feature? I am doing a down, then across arrangement, and one group's information will span both columns (I have two defined), and I'd like the group heading for the group that is spanning both columns to repeat at the top of the second column. I already have 'Format Groups With Multiple Columns' checks on the Layout tab.. and that works fine except for repeating the group header at the top of the second column. Thanks in advance for any ideas...

 

[synapsevampire]

Also right click the group and select change group->Repeat group header on each page.

-k

 

[JLZ99]

Thanks, but I already have that turned on.. and it does repeat the group header on the left column of a new page.. But, on a single page, if the group does not change and spans two columns, it won't repeat the header at the top of the second column.. it will only put a header in the right column if the group change happens to fall in a right column.. I put an example below... What I can't get it to do is put the "Group A Con't" piece when a single group spans two columns on a page...

Group A Group A con't

xxxxxxx xxxxxxx
xxxxxxx xxxxxxx
xxxxxxx xxxxxxx
xxxxxxx Group B
xxxxxxx xxxxxxx
xxxxxxx xxxxxxx
xxxxxxx
xxxxxxx
--------------------- End of Page

 

[synapsevampire]

Ahhh, sorry, I misunderstood.

Columnar headings aren't a part of the design.

You might use a detail section prior to the usual details which can use a {table.field}+" cont..." and create a counting formula which suppresses accordingly.

-k

 

[JLZ99]

Thanks... I had a feeling it wasn't do-able... but, I'll play around with what you have suggested..

 

[bdreed35]

I have done this in the past and trying to recreate it. Give me some time and I will post the solution when I dig it up.

~Brian

 

[JLZ99]

Awsome.... I will definitely keep checking then... thanks

 

[synapsevampire]

Brian: You can create a formula in the details section which uses a suppression criteria based on the number of rows per column.

Keep in mind that the counter will have to count the header as well.

-k

 

[bdreed35]

I jumped the gun. What I had done in the past was only with columns, not with Groups with multiple columns. We basically had a 2 column detail section. If the data did not print in the second column, we needed to suppress the second columns header.

I apologize for getting your hopes up.

~Brian

 

[JLZ99]

Well, thanks for taking the time to look.. I'll keep Vampire's suggestions in mind and try a few things with that... I appreciate the fast response...

Jamie

 

[synapsevampire]

If I get some time I'll work it out for you, I'm giving classes and trying to get 36 new Crystal developers up to speed, so my time is short, I'm mainly just posting theory.

-k

 

[vidru]

I've been playing around with this for the last hour or so. I've got two samples (one using HTML text, the other with no text interpretation) that were written in 8.5 using the Extreme database.

Short on elegance, but it's a start!

I can send them to you, just say where.

-dave

 

[lbass]

Here's another approach:

This assumes that you have two columns, with format in multiple columns checked, and in the layout section, format groups with columns is checked. As SV noted, the repeat group headers on each page should be turned on.

First, insert a second details section_b. In design mode, magnify the view so that you can ensure that the group header and the two detail sections are exactly the same size. Suppress the report header (or start a new page after), and suppress the group footer, if you're not using it.

Create two formulas:

//@reset} to be placed in the page header:
whileprintingrecords;
numbervar linecnt := 0;

//{@linecount}:
whileprintingrecords;
numbervar linecnt := linecnt + 1;

Place this last formula in the Group Header, Detail_a, and Detail_b. Place the fields you want to display in the detail_a section. In the detail_b section, copy the GroupName that is already displayed in the Group Header.

Next note the number of records you are getting in the first column of each page and also note the last number on the page. In this example, there are 58 records in column 1 and a total of 115 on the page.

Then go to the section expert (format->section)->detail_b->suppress->x+2 and enter:

remainder({@linecnt},58) <> 0 or
previous({table.groupfield}) <> next({table.groupfield})

Then still highlighting detail_b, go to "New Page After"->x+2 and enter:

not onlastrecord and
remainder({@linecnt},115) = 0

-LB

 

[vidru]

Slick, LB... *.

The I'm was doing it is similar, but not quite as clever. I'm suppressing the group header and footer, and using a formula in the details section to print the header/fields based on the line number.

-dave

 

[lbass]

Thanks, vidru. I'm interested in your approach--can you describe it here?

-LB

 

[vidru]

LB,

Using the Extreme database's Customer and Orders tables.
Grouping on {Customer.Customer ID}, data field {Orders.Order ID}
Record Selection Formula: {Customer.Last Year's Sales} > 200000

Same as you, I have an @Init formula that declares/resets a variable (linenumber) in the page header.

Figured out that I can have 52 rows per column. Suppressing the Report Header, and Group header and footer.

Created a formula in the Details section to display the header (if necessary) and the data field, as well as "cont." if the group spans more than one column, or is continued from a previous page. I'm incrementing linenumber inside this formula (if the group header will be displayed, then the linenumber increases by 2).

For some reason, it's not letting me post the @Display formula (???). Anyway, the @Display formula uses if statements to determine where it is in the report, what to display, and how it should increment the line numbers (by one or two).

-dave

 

[JLZ99]

Thanks so much for all of the great tips guys... Lbass, I tried what you described, and after I got all the sections the same size, your solution worked perfectly. I also tuned it a bit to place the 'Continued' in the appropriate places. I had most of what you described, but I didn't have the 'previous' and 'next' logic or the onlastrecord logic. Thanks again for all of the help, it is greatly appreciated.

Jamie