Are you searching for related records or parent records? Searching for related records can be slower.
The other thing to check is the indexing on your search fields. If FileMaker has to build the index for each field you're searching on that will take time. Searching on an un-indexed, related field will take even longer.
One other thing you may want to try is instead of performing searches, view the records through a portal. You're capturing who the user is and the portfolio of records. It should be easy to set a portal to view the corresponding records. Then if you have to view the details for this record a simple Go To Related Record script on the portal row can isolate it on a form view layout.
Same functionality - no searching.
Thanks for teh responses David and sorry for the delay getting back.
The field is indexed. The purpose of the find was to hide all of the <no access> records from the users view. After some more searching it looks as though I was going about it the wrong way. Looks like FMs recommendation is to use a self join. After spending some time learning SJ I think I have it working ... almost. Now the user only sees the records associated to the portfolio they picked upon entering the system. The other records are still there but instead of <no access> the records are just blank. Looks like I might have to use a find after all.
Not sure I have the self join setup exactly right. Problem is the users are not tied any records. User1 might own portfolio 1234 this month but next month they might move to another account and so the user that views and updates the records would change. The only thing that never changes is the portfolio that the record is tied to. So portfolio 1234 might belong to bank of america and that won't change. It would be a rare case if it did.
I just want the user to be able to select a portfolio when they eneter (that part works) and then all other modules would then only show records tied to the portfolio number.