If the function works nearly instantly and the portal takes a while,
then it is because you have applied sorting to either the portal or to
the relationship that the portal is based on. I guess my question to
you is what is it you are really trying to accomplish? Why are people
intentionally searching on criteria that would result in 5000 records,
and then why would they want to scroll though 5000 portal records to
find what they're looking for? There are likely much better ways --
much more efficient programmatically and much more intuitive for the
users -- to accomplish whatever it is you are trying to accomplish.


Carlos Pereira wrote:
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg (818) 883-2846
FM Professional Solutions, Inc. Los Angeles

FileMaker 8 Certified Developer
Associate Member, FileMaker Solutions Alliance

On Tue, 20 Feb 2007 09:31:47 -0800, Howard Schlossberg
<howard (AT) antispahm (DOT) fmprosolutions.com> wrote:

I got it! Neither the portal nor the relationship the portal is based
were being sorted. The problem was context. I am using the Anchor-Buey
graph method, but the layout was not based on the anchor TO. This
dramatically slowed down the portal refresh time. I've changed the
layout to be based on the correct TO, and everything is working fine
now. Both the search and the portal are almost instantaneous (less
than one second) which is exaclty what I was looking for. Thank you
very much for your help on this. I have added some comments bellow
FYI.

I am building a project management solution. The user might want to
browse all active projects, all his active projects, or all projects
for a given client, month, etc. The number of projects returned in any
of this searches could range from 0 to 800 (or maybe more, I do not
know it in advance). I am pushing the system to the limits to see how
it does.

I cannot control how many records are going to be returned by this
kind of searches, and YES, the user wants to see all the records,
because moving back and forward record by record is useful but not
practical when you have a found set of 500. I could try to filter the
found set, but for them is not acceptable. The idea of the portal is
to allow them to easily jump to a given record. This is not exactly a
request, but a requirement given their current needs.

Thanks