Karen, What an awesome idea! I would love to see this kind of break control implemented. It would be so elegant.
In the past, I have forced the sort order at the print command level but I had to make sure to maintain that sort order very carefully as the report was modified. Your suggestion truly places ALL the control in the report breakpoint definition which makes maintenance a snap rather than a chore. Another enhancement to that idea would be a flag to indicate if NULLs should come first or last in the sort order, settable on each individual breakpoint along with the ASC/DESC option. Dennis McGrath ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, April 28, 2008 3:56 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Illegal Column Specification Breaks ARE the "sort or order by". You can define a whole bunch of breaks, not locating a single thing in a break header or footer, just to have it sort a particular way. So just put your date as another break level, "below" the break levels you already have by building and floor. The only case that this will not work is if you want it to sort Descending. Breaks always sort ascending. Hmmm.... never thought about asking for a descending break; dates would probably be the only place where it might be desirable..... Karen However all I can get is the report to group by building and floor and then start new page breaks then, but it completely ignores the date being sorted. I do not see anything in the break to do any type or sort or order by.... ???
