Newbies Sally1 Posted July 11, 2008 Newbies Posted July 11, 2008 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.
Newbies Sally1 Posted July 11, 2008 Author Newbies Posted July 11, 2008 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.
bcooney Posted July 11, 2008 Posted July 11, 2008 I don't understand the need for the zc_date_low/high fields. Why not just have the two global fields filtering the portal?
comment Posted July 11, 2008 Posted July 11, 2008 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.
Recommended Posts
This topic is 6036 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now