Navigating to portal rows with no vertical scroll bar?

[HALBURN]

I have a portal that displays 10 rows with no vertical scroll bar. There are approximately 200 records in my table occurrence. I want my users to navigate by clicking on buttons, similar to the navigation in this forum. (please see attached screen capture)

When I try to use a "go to portal row" script step it does not work becuase it only allows me to choose records being displayed (portal rows 1-10). Is there a way that can I display records 11-20 without changing layouts, and without showing the vertical scroll bar? Unfortunately showing the scroll bar, or even turning it on and making it transparent is not an option with this particular solution.

[comment]

See:

http://fmforums.com/forum/showpost.php?post/201804/

http://fmforums.com/forum/showpost.php?post/356203/

[HALBURN]

Thank you, I will check those out.

[HALBURN]

I realize that I can hide the portal row to prevent the user from scrolling but this also prevents me from using the “go to portal row” script step if I want to display records outside of the ones currently visible in the portal.

My original goal was to have buttons that the user uses to navigate forwards and backwards through the portal records without having any portal scroll bars at all (not even invisible ones) so I can butt a graphic right up to the right side of the portal row with no gap.

I have experimented with some workarounds that are based on displaying a targeted range of portal records using the record IDs and a global match field, but this breaks my solution because I am also applying real-time filtering and sorting options to the portal.

Does anyone have any possible workarounds to this problem?

[Ocean West]

You are trying to introduce Pagination to a portal and include a Live Filter... I believe you will need two relationships, the first one is where you will do the filtering that relationship may provide you say 25 results.

(when i mention live filtering this is not using FMP11 portal filter feature - rather you are using keys or multi-preductate methods to filter related items)

You would push the first five ID's of that portal in to a global field that is the basis of your second relationship global id ---< id

you could store the value of the page you are on in a $$variable or another global field - when your user pages up or down based on the current page you

would get the previous or next 5 ids from the filtered relationship.

You would need to clean up or add triggers on leaving or on entry to the record / layout the variable - so that when scrolling thru record everyone starts on the first page.

hope that helps -

here is another tip... http://www.gaslowitz.net/filemaker/blog/2008/07/video-paged-data-with-resizable-portals/

[comment]

This seems to be a follow up to:

http://fmforums.com/forum/topic/81961-navagating-to-portal-rows-with-no-vertical-scroll-bar/

[Ocean West]

topics merged.

[HALBURN]

Sorry, I created a new topic because I was trying to get a specific answer about how I could lock a portal to prevent a user from scrolling. I had given up on removing the portal completely because none of the techniques that I have experimented with seem to work with the type of filtering and sorting that I am doing. Currently, I have made the portal row invisible but the user can still scroll it with the mouse wheel. The user's scrolling prevents me from getting the exact position of the portal that they are selecting...which is actually one of the main reasons that I am trying to get rid of the scroll bar all together.

If you have admin access could you please correct the typo "Navigating" in the subject, I am unable to edit it?

Thanks for your suggestions and links.

[Ocean West]

if you have a button on the portal row you can certainly get the Get ( ActivePortalRowNumber ) and pass that to the script to perform action?

[comment]

none of the techniques that I have experimented with seem to work with the type of filtering and sorting that I am doing.

I don't see why not - it just requires more work. At some point, you need to perform GTRR from the filtered portal and collect the IDs by looping.

Currently, I have made the portal row invisible but the user can still scroll it with the mouse wheel.

If the portal has a scroll bar, then the user will be able to scroll - unless you hide the scroll bar AND deny entry to the portal.

[HALBURN]

I have a working solution but I am not very happy with it. It requires a script that loops through and numbers all of the records. It's fine if you only have a few hundred records but not very practical if you are dealing with 20,000 records, which unfortunately my client is.

I can't believe that I have to choose between showing that stinking scroll bar (or using a ridiculous looping script) just to give my user the ability to navigate back and forth between a found set of records in a portal row.