Hi Jeff,
It's tricky because calculating examples can be "expensive" in terms of time.
Currently the totaling is designed to be "total this page". That's fast and has no impact on performance. If you want more than that you can do it, but obviously you will want to balance speed with usefulness.
>> I experimented with custom totals
This is indeed the way you should go. Usually I create a simple source procedure to calculate the value I want.
>> Ideally, I want to display 10 rows on each page, with a "partial running" total but then a final total on the last page, under the "partial running" total.
I think a partial running total would be difficult (or expensive) to calculate. What if the user goes next, next, previous, next, previous, last? you can't simply keep adding pages to the running total. What if they just click on "last"?
I'd drop the idea of a running total, and just focus on the grand total. You can calculate this the first time the browse opens (tie to the filter and session - if the filter changes you need to re-calc the total). Then set the custom total to this value.
I can go through this with you in a user group webinar if you like. (Of course calculating the total may take a few seconds when the browse opens, depending on the size of the data being totaled.)
Cheers
Bruce