| Subject | Re: snake report observation |
| From | Mervyn Bick <invalid@invalid.invalid> |
| Date | Thu, 1 Dec 2016 22:51:26 +0200 |
| Newsgroups | dbase.getting-started |
On 2016-12-01 10:23 PM, Ronnie MacGregor wrote: > In article <i7I4Ke9SSHA.2980@ip-AC1E04A7>, invalid@invalid.invalid > says... > >> This meant using a temporary >> table so I could add a dummy record and a field to act as a groupBy >> trigger for the extra group. > > Not really been following the detail of this thread, but . . . . . > > Would a calculated field added to the rowset work for this ? > No, I'm afraid not. The requirement was to print a list of 3-ball and 4-ball golf matches in two columns and then print "Additional matches" after the last match. The idea was that any extra matches wold be written in by hand. (I suggested a way to print them instead but Charlie didn't want that.) The reportgroup footerband is the ideal place to put the heading. One needs to check if there is enough space in the streamframe after the last match. If there isn't then the heading must be moved to the next streamframe. The calculation is easy enough but unfortunately dBASE doesn't immediately force a move to a new streamframe if the reportgroup footerband preRender event handler sets the beginNewframe. To get round this I nested the original group used to separate he matches in a second group. The heaaderband event handler does force a new streamframe immediately s that was one problem solved. To trigger the outside group it needs a field that has a value for all the matches and changes after the last match has been rendered. This was why I needed a temporary table that I could add a field to as well as a dummy record that would trigger the outside group so that its headerband would become available. This headerband preRender does force a new streamframe if necessary and then the inner group headerband which would normally announce the match with the dummy record is used to print the heading. "Messy" but it works. :-) Mervyn. | |