I am using FM 11 adv in OSX

I have a portal with 2 portal fields: Date Reading

In the same table I have: Maximum, Minimum and DIfference (Maximum-Minimum) fields

The portal is sorted in Ascending Date order.

The problem:

I have a water meter reading application.

There are 2 tables: PROPERTIES and METERREADING (one to many)

On a layout based on PROPERTIES I have a portal based on METERREADING.

When I add a new 'row' to the portal, I enter the Date and the Reading.

This puts the 'new' row at the bottom of the portal.

I need to, in script, 'refresh' the portal so that the new 'row' is put in the proper sequence

so my script can find the MAXIMUM and MINIMUM.

I tried REFRESH and that doesn't work.

I tried jumping to another field and back and that doesn't work.

What is the 'trick' to getting the portal to 'refresh' after adding a new row?

Use the Commit Record/Request script. Then Refresh Window with the flush cached joins option selected.

Use the Commit Record/Request script. Then Refresh Window with the flush cached joins option selected.

Works great. I have tried those two commands but not consecutively. Is being consecutive what drives it to work?

Thank you for the assistance.

The commit step closes the record and updates the data. The "flush cached joins" option of refresh window step make FMP re-calculate all the relationships and portals.