Fields in HEADER pull from LAST record, not first?

Trying to print a form with a calculated/stored field in the HEADER portion. It is merely a single letter - A, B, C, etc. I assumed that placing the field in the HEADER would show the field relating to the first record on the page, but it defaults to the LAST record.

Even updated the foundset, then removed the calc (so just a stored field previously calculated)

So, if 5 records fit on a page, 8 records total

They have letter fields that are A,A,A,A,B,B,B,B

DESIRED

A
Record 1 (A)
Record 2 (A)
Record 3 (A)
Record 4 (A)
Record 5 (B)

B
Record 6 (B)
Record 7 (B)
Record 8 (B)


SERVOY OUTPUTS

B
Record 1 (A)
Record 2 (A)
Record 3 (A)
Record 4 (A)
Record 5 (B)

B
Record 6 (B)
Record 7 (B)
Record 8 (B)


We’d like to show A in the header, but instead B shows.

If they go A,A,B,B,C,C,C,C , B then C shows.

DESIRED:

A
Record 1 (A)
Record 2 (A)
Record 3 (B)
Record 4 (B)
Record 5 (C)

C
Record 6 (C)
Record 7 (C)
Record 8 (C)


SERVOY OUTPUTS:


C
Record 1 (A)
Record 2 (A)
Record 3 (B)
Record 4 (B)
Record 5 (C)

C
Record 6 (C)
Record 7 (C)
Record 8 (C)


Wouldn’t it be better to have the HEADER show data from the FIRST record, and FOOTER show data from the LAST record if they’re not a summary field?

We don’t want to use a leading summary, as this will not stick to the top of the page.

Any ideas on if this is possible? and why the default is counter-intuitive (printingwise, I understand the underlying SELECTED record (in this case being the last record) defaults of servoy)?

Lastly, I’m going to try a few summary field stuff (do max / min work on alphabetical fields? I’ll soon see :slight_smile: ) to achieve the same thing.

Thanks!

NCM
FSCI

MAX MIN aggregates do work on alphabetical text fields. :slight_smile:

BUT, no go…can’t get any permutation of headers, summaries, etc, to show the correct letter at the TOP of the page.

Sub-summary, grouped on the letter field, works fine but this is a long list so many pages show NO letter - the sub-summary displays, then on the next page it doesn’t show anything, and on, until the letter field changes again - which is expected behavior, but doesn’t help me.

Grand summaries don’t seem to be useful - they’re just a foundset (rather than page) header field that doesn’t display until you print it seems.

As the HEADER is a page header, it would make sense to have it display the FIRST records data, not the lasts.

Filemaker would always display intuitively when placing fields in a header or footer section.

NCM
FSCI