I have a solutions where I created a portal to show duplicate records, records that have the same name. We use this to determine different version of master recording. It allows us to see what is a duplicate vs. just another version.

My problem is I have the portal sorting by song title and it constantly resorts. I have a button/script in the portal that takes you to the related record so you can see more of the data about that song. When you click on the button the portal resorts. Then you click on it again, it resorts then you can click on the button and it takes you to the related records...then it resorts again.

This also happens when you try to scroll the portal. It resorts, then allows you to scroll.

VERY ANNOYING!!!

This file is huge and is showing 11,000 records. But I feel once it sorts initally, why is the portal resorting?

It is also being server by FM 6 Server. Everything else is working like a charm.

Both the server and machine running this solution (remotely on a LAN) are G4 dual 1.25.

Thoughts?

I have noticed this problem with FM5/6 portal sorting, especially if the sort uses multiple criteria, unstored calcs, or if the network is slow (10Mb or slower.)

Some possible solutions are to upgrade the network, don't sort the relationship the portal uses (probably would not work so well for your case,) or use filtered portals to reduce the number of records in the portal.

FM7 does not appear to have this problem.

It's to do with the sort order that's set in the relationship definition. The sorting is only noticeable when the related record count gets into the thousands. Probably nothing you can do about it: you have asked FMP to sort the related records, and that takes time especially over the network.

As Ender suggests, the ultimate solution is remove the sort from the relationship. Second best is to reduce the number of related records seen in the portal at any one time.

I was just wondering how anybody could possibly have thousands of related master recording records, then I noticed you are from Warner / Chappell Music... makes sense now!

FMP 7 is meant to be much, much faster at indexing and displaying records.

My interum solution was to create an unsorted version of the layout and relationship, so the user can opt not to have it sort.

I was thinking about the filtered option as well, but haven't had a chance to implement since there are always 4-5 people using the solution.

Thanks all!

>>I was thinking about the filtered option as well, but haven't had a chance to implement since there are always 4-5 people using the solution.

Pesky users!