Ed Leafe wrote:
> On Saturday 30 July 2005 10:59, Paul McNett wrote:
>
>
>>I've anticipated the desire to have an unlimited number of detail bands
>>and groupings, to lay them out separately, and to conditionally print
>>one or more detail bands. The designer interface to each of these
>>elements could indeed be a pageframe. A "page" on a report doesn't
>>necessarily have a 1:1 correlation with a "band" (but it could). Am I
>>understanding the vision correctly?
>
>
> It doesn't necessarily have to span the width of a printed page. Also, let's
> not confuse the printed page with the pageframe page: that's an unfortunate
> collision of terms. I'll write the pageframe 'page' in quotes to distinguish
> them.
I am also wondering if it makes sense to think of bands as something that spans
the whole page. A grid doesn't span the width of a form, nor does a text blob(?)
that expands downward as needed. I am a little foggy on how this would work in
the report designer and output, but I think there is something worth exploring.
>
> Carl's example of address formatting is perfect: arrange a series of fields
> and labels on each pageframe 'page', with one 'page' for each different
> country format. When the report executes, it will evaluate a condition
> property of the pageframe, and use the layout for the particular country's
> address.
exactly.
>
> The area controlled by the pageframe could be small, or it could conceivably
> cover an entire band. Now when you have a pageframe on a 'page' of another
> pageframe... then it gets interesting!! ;-)
bah... not if it is coded well ;)
^C
©2005 Carl Karsten |
