From Dwayne Wright PMP
Certified FileMaker Developer
Please Note: If you are viewing this page in a news feeder, the images may get munged up a bit. For the best experience, please visit the journal directly by clicking (here).
A READER ASKS
I know my comment on this is really outdated, but I've read your blog post while looking for a solution to my problem which is related to alternatives/solutions for listview in IWP and I have a question.
What I'd like to ask is:
Is it possible to implement a "List View" alternative with a portal for IWP use, but without a scroll bar? I was thinking of a portal showing a standard number of rows and using a scripted "switch" to show next/previous set, much like a CWP page would look like (with much less functionality though I admit)
I thought of a CALC field in the related table which sets a value of Get(RecordNumber) that is then used to filter records through the parent table layout. However I can't put it to work. Can you tell me please if it is possible so I don't waste my time in a MI-problem?
There isn’t a way to scroll a portal without a scroll bar (that I’m aware of). Depending on how many records you might be showing in a portal, you might try showing the same portal with a different starting row number in different tab panels.
For example, one portal can show you related records 1 through 18 and the second portal (using the same relationship and fields can show you records 19 through 36.
Here you can see the dialog box setup with a different starting portal row number.
You can identify a layout object (like a tab panel) with an object name then the Go To Object script step will take the user to that object, be it a field, a button, a tab pane, the web viewer and more! You do need to make sure that all your objects are unique. You do have the script parameters to specify the object you want to go to (and this can be a calculated value, how cool!) and what repetition of the object you want to go.
You can put a big object on top of the tab panel to hide it from your users. Then the coding would be to set a variable equal to the last row number. When the user clicks the button to view the next set of portal records, the script would go to the tab panel that has that associated portal.