Paginate 1-15 16-30... without next link?

Question

I have a report with more than 100 rows in it on some occasions, I have selected Pagination Scheme of Row Ranges 1-15 16-30 (with set pagination) under Layout and Pagination on the Report Attributes tab.
My problem is with that Next > (and < Previous) link, that appears, when there is more than 75 rows on the report. I understand the meaning of it, but I would like there to be just links 76-90 etc following the others NOT the link Next, because:
* it might confuse some users, who would think that it leads to the next set of rows not the next set of pagination (eg when viewing rows 1-15 they would expect it to go to rows 16-30, but what it does is to change the pagination set)
* when looking at a pagination like this I don't know whether there are just 76 rows on the report or over some 1000
* it appears to be absolutely uncustomizable - I would like to change the image of > to match my web design, but I haven't found a way (except for changing the very image in HTMLDB image directory, which I don't want to do, because some other apps use the same picture and renewing HTMLDB version probably replaces it again). And, I would like to translate it into estonian, but that is also impossible.
So, is it possible to have all row ranges without that next link? Or is it possible at least customize the link so that it would look as if intended on the place? Or is the only way to make my own pagination with Use Externally Created Pagination Buttons (or is it impossible even then?)?

Answer 1

though the current implementation of that row ranges pagination scheme doesn't let you not show those previous and next links, you'll find quite a few pagination template customization options available at the bottom of the report template definition pages. you'd be able to enter your estonian Next and Previous strings there, too. you could also consider using application level substitution strings for those Next and Previous strings. that way your app would be more translation-friendly. so you'd define app-level sub strings as something like MY_NEXT_TEXT and MY_PREVIOUS_TEXT and you'd refer to them in your report template's pagination section (in the "Next Page Template" and "Previous Page Template" fields) as &MY_NEXT_TEXT. and &MY_PREVIOUS_TEXT.
hope this helps,
raj