Hi,
As I've read here in some other threads there are people who try to limit the number of displayed rows in a table over multiple formatted pages in WebI. And there seems to be no satisfying solution yet.
Problem
There are m data rows retrieved from a query which are to be displayed in a table showing max. m table rows each page, no matter how the table is organized.
Near solution
As already described in a different thread you can define a (hidden) column for the table with floor(rowindex() / m) and make a page break through a group. This seems to work quite well.
But
As long as you do NOT define any sort over a different table column than the grouped one this really works. But if you have one or more columns which HAVE TO be SORTED PRIOR the grouped column the solution described doesn't work. It somehow mixes up the different table parts on serveral pages in a manner you won't expect. In short, the result is not acceptable.
Please
Do not think this problem is solved by limiting the number of returned rows PER QUERY or the max. number of rows PER PAGES through some WebI options. This is NOT the solution as it's about DISPLAYING a table's rows and not about limiting retrieved data rows.
My guess in this case... it's IMPOSSIBLE to create such a page spanning table, though it would be more than just nice to have such. But I try to learn ;-).
Thanks a lot for any hint using BO WebI Rich Client 4.1