I have a table occurrence for customers-invoices which uses the following criteria:

_kp_customers_id = _kf_customers_id

zc_date_low <= order_date

zc_date_high >= order_date

When I change the dates, the portal records don't update based on the new filter critera. If I leave the layout and return; however, the records on the portal are correct. I am assuming that the criteria is working properly, there is just something that keeps the portal from updating after changing the criteria. What am I missing?

Thanks.

Are zc_date_low/high storage option set to global?

No, the zc_date_low and zc_date_high fields aren't global fields, but they are calculated fields based on globals. In other words, the user enters the dates into a global field and then these fields calculate the date (so that if one of the global fields is empty, the calculation puts in a value.) If I make the zc_date_low and high fields globals, the calculation doesn't update.

I don't understand the need for the zc_date_low/high fields. Why not just have the two global fields filtering the portal?

This would happen if the globals are defined in another table. Filemaker doesn't detect that modifying the globals is supposed to have impact on the relationship, so it doesn't recalculate.

Either put the globals in the Customers table, or include a Refresh Window {Flush cached join results] step after modifying the globals.