Paul:
I feel your pain still, after all these years.
Vojo:
Not sure what you mean. There's still that 50-row limit.
However, reading through this old thread got me thinking about a possible solution based on a recent project I did. In it, I create literally hundreds of User section rows. I was originally concerned that too many rows would slow things down, but a test showed it takes
thousands before you begin to notice any degradation.
Since there's effectively no limit, that got me to thinking that I could put the names of the 100+ pages into the User section, one page to a User row, with row names like User.Caller_1, User.Caller_2, etc. In the Action section, I can create 25 rows that use User.Caller_1, etc. as their target pages. To access the next 25, I can add a factor that is used to build the target page names in the Action row such that instead of User.Caller_1, etc., it calculates the page name as User.Caller_26, etc. That way, the existing 25 Action rows can be used to reach every page in batches of 25, thereby respecting the 50-row limitation and leaving room for other actions as needed.
I haven't tried to build the beast, but I suspect the Actions.Action would look something like...
=GOTOPAGE(User.Caller_" & 1+(25*(User.PageNumber-1)) & ")"
=GOTOPAGE(User.Caller_" & 2+(25*(User.PageNumber-1)) & ")"
=GOTOPAGE(User.Caller_" & 3+(25*(User.PageNumber-1)) & ")"
etc.
...where Next and Previous actions would increment and decrement User.PageNumber, respectively. Looks like I might have to put each target page name formula in its own User row, but I think the example above gives you the general idea.
So with only 25 action rows, I can have
thousands of available pages I could jump to, with a choice of 25 at a time; and it could be built as a flyout to keep things out of the way until you needed it.
I'll check back in if/when I implement it. Right now it's not crucial to anything I'm doing, so it goes on the list. But it looks like it'd work. We'll see...
- Ken