It's not as simple as putting the current page number on your layout--which does not require a field to do so--but might prove useful for getting what you need here.
Do you have any fields or portals on your layout that are set to slide up and resize the enclosing part?
If not, the number of records and the number of sub summary layout parts (if any) can be used to calculate the number of records to each page and you can then set up a sub summary layout part that prints at the bottom of each page. Then summary fields can be placed inside this sub summary part to display page totals.
On every page, 20 records are showing, and it wil continue on the next page, until it runs out of records. It is done by putting fields in the body and the setting "Page break after every 20 occurrences". What I want is the records (which are all different values) at the end of each page added up.
Make sure that you can still fit 20 records on each page once you add the page totals to a sub summary part in your layout.
Here's a simple calculation that can be used with this method to calculate the page number when in browse mode:
ceiling ( Get ( RecordNumber ) / 20 )
We can call that unstored calculation field "cPageNumber"
Then add a sub summary part "when sorted by cPageNumber" to your layout and add the summary fields needed for your page totals to this new layout part. To see the page totals, you'll need to sort your records by cPageNumber.
Also, remove the "after 20 occurences" setting on your layout body and specify "after every 1 occurrence" for the new sub summary part.
I'm not shure what I am doing wrong, but it still shows the total of all the pages instead of only one. Can I send you the database so you can see what I mean?
is the field pointed to by the red arrow a field of type summary?
Is it inside a sub summary part?
The field at the red arrow is a calculation [Sum ( Artikelen::Totaalprijs )] (Artikelen::Totaalprijs is the green arrow) and the field at the red arrow is inside the sub summary part
It should not be a calculation field. This should be a field of type summary instead.