What happens when you combine both the portal sort and the filter? Does the filter happen before the sort?
You might try opening Manage | Database and specifying the sort order in the relationship rather than the portal set up and see if that works.
Sort the relationship in the relationship graph, not the portal in layout mode.
Like what Phil said, he just beat me to it......
1 of 1 people found this helpful
I was able to produce the results that you want, but not using your methods. Get ( RecordNumber ) reports the current position of the record in a found set or portal. But when used in a stored calculation like you have, it captures the record's position at the time it was created, not what it might be at a later point in time in a different found set or portal and possibly with a different sort order.
If I change the calculation to specify that it be unsorted, however, I don't get anything that works.
What did work, was to add a simple number field to table 2, go to the Table2 layout and add that field to it, sort the records in alphabetical order, then use replace field contents with the serial number option to assign a number sequence to the records. I could then modify your filter expressions to refer to this field instead of the original count field.
There are obvious draw backs to this approach--namely that any additions/deletions/changes to Table2 records would require renumbering them.
You might consider replacing your two portals with a whole series of unfiltered one row portals. Your top left portal would specify row 1 as its initial row. The top right would specify row 2. The next left row 3 and so forth...
I actually will only be edit the records in the related table when viewing them in their home table, so setting a trigger to renumber them should do the trick. Thanks!