Re: Header/Footer - 02-23-2004 , 09:44 AM
though I don't think
Re: Header/Footer - 02-24-2004 , 07:09 AM
In article <20040223154419733+0000 (AT) news (DOT) blueyonder.co.uk>, Alan
<braedsjaa (AT) yahooooo (DOT) co.uk> wrote:
hundreds of records. A header is a good place to park releveant data
about what the list is. Also, a header is a good place to put navigation
& script buttons, so after you scroll way down, you don't have to scroll
all the way back up to click a button.
There are some strange effects that show up, like placing global fields in
a header part can mess up somes kinds of scripts. I've found I have to
put these fields in the list body, way off to the right, text set to white
so they don't show.
Regular fields work great in a header. One use is a running total field
for scrolling through long, long lists of products to order. As you make
selections, your accumulated progress is always visible.
Re: Header/Footer - 02-24-2004 , 03:58 PM
Put the most important information in the body; the lesser stuff can be
relegated to headers or footers (these fields will reflect the currently