reference previous sumation field

[stormin_norm]

I have a report which is summarizing every semester. I have to display "Past credits" which are the credits sum'd up to that semester.
Is there a way to reference the summation field of the previous detail section.
Or put an invisible summation field in the header??

quick example of this issue:

subreport shows:
transfered credits = 53

main report:
semester 1
attempted credits=10
past credits=53
earned=10
cummalitive earned=63 (53+10)

semester2
attempted credits=14
past credits=63
earned=12
cummulative earned=75

Thanks!!!!
-norm.

 

[WayneRyan]

stormin',

You can put hidden controls whereever you want. Make them
running sums if you want.

You can use events on reports like forms. There are DetailPrint
and Format, as well as page and report headers (and footers).

Experiment.

Wayne

 

[stormin_norm]

Thanks for the directional...I'll try the header section, maybe more fun
I also found by putting fields in the footer with value = sum(xxx), I never use the runningsum property. Only in one report I used running sum for enumerating students.

I tried on another report to mess with loading some values during the print event, but it worked better in the format event.


Is it true the format event is triggered, after all detail records are created. Then the group footer would perform its summation.

Or does the format event trigger for each row of detail. I thought in the solutions crosstab example there was a parameter passed to the format event to 'stop' the fields from being triggered to .visible=false.
In any event (smerk), my dynamic crosstab worked great using the format event vs. print event.

Now that I'm typing....I'm not sure when you would actually use the print event. Once the report is formatted, I don't have a need to mess with print settings.

-norm.

 

[WayneRyan]

Norm,

I posted this a while ago, while researching the order in which
A2000 fired its triggers.

http://www.access-programmers.co.uk...adid=47142&highlight=wayne+and+event+and+2000

Wayne

 

[stormin_norm]

nice complex example Wayne!

My report is running fine. Using some 'higher math' subtraction and a few invisible fields.

I was thinking the header section would be 'initialized values' vs. the footer. But all fields sum up the same in both sections.
Therefore, I have to conclude the header section is calculated after the detail the section has been created. And not sequentially.

I noticed you and the solutions example like to use a phase variable in the header/footer sections. I guess it is the only way have it 'fire' once or twice.
I wound up formatting everything in the onReportOpen. And it worked fine. Basically just setting the record source and visible=no.

fun stuff

 

[WayneRyan]

Norm,

Well I didn't think the experience was that fun. I had to have
a heading contain something depicting the contents of the
detail records. The DetailFormat fires too many times. It fires
one "extra" time per page, just to see that the line won't fit.

That is why I needed to catch it on the second pass, cause
by the time the DetailPrints are done, the heading is too.

Wayne