And to think about it farther, it makes perfect sense that the page style would 
be the first evaluated – it establishes the page onto which everthing else is 
written.  It has to be first.  If you tried to do it last, how would you get it 
to go behind everything else?  Wouldn’t work.

 

The deceptive thing is that the page style band is at the bottom of the 
designer rather than the top.  It leads one to think that it gets processed 
last, given our “top-down” reading of the page.

 

Emmitt Dove

Manager, Converting Applications Development

Evergreen Packaging, Inc.

[email protected]

(203) 214-5683 m

(203) 643-8022 o

(203) 643-8086 f

[email protected]

 

From: [email protected] [mailto:[email protected]] On Behalf Of Emmitt Dove
Sent: Thursday, March 26, 2009 4:06 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: How to make page-style label visible / invisible

 

Larry,

 

In one of my previous messages on the topic I noted that the page style band 
appears to be the very first one evaluated, so if you want to change something 
displayed on it, you would have to be able to code your logic that way.  

 

Emmitt Dove

Manager, Converting Applications Development

Evergreen Packaging, Inc.

[email protected]

(203) 214-5683 m

(203) 643-8022 o

(203) 643-8086 f

[email protected]

 

From: [email protected] [mailto:[email protected]] On Behalf Of Lawrence Lustig
Sent: Thursday, March 26, 2009 3:12 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: How to make page-style label visible / invisible

 

<< 

The BEFORE GENERATE eep will evaluate variables in the current band and allow 
you to manipulate things before they are “committed to the page.”  The AFTER 
GENERATE eep does not permit you to impact the display of the current band.  
AFTER GENERATE would be useful for example in conditionally accumulating totals.

>> 

 

Thanks for the update, Emmitt.

 

I'm able to affect the contents of any particular band _except_ page style by 
putting code in the ON BEFORE GENERATE EEP of that band (or any band that 
precedes it in rendering order).  But I still can't seem to find the right 
place to put code to affect the contents of the Page Style band relating to the 
current set of data.  If i change something on the page style band, it affects 
the NEXT page.  From this I surmise that page style is evaluated before 
anything else.  I could use some "look ahead" code to try to figure out what 
the critical values will be on the next page of the report and update the page 
style that way, but I think it would be unmaintainable.

 

I did do something like this in the past but looking it up, I see that I placed 
the watermark in a band footer in that case, rather than the page style band.

--

Larry

 

Reply via email to