again, Commit Records is the step to use to 'force' an update - use it in a triggered script in required fields
1 of 1 people found this helpful
Using a calculation field defined in the layout's table which uses the sum function to create this total will update more smoothly than a summary field defined in the portal's table.
Following symbister's advice, I created modified the "Quantity" field to have an "On Object Exit" Trigger. That Trigger performs: "Commit Records/Request [No Dialog]". Upon testing, I see that the Trigger only works about 75% of the time. In other words, about 75% of the time that I change the Quantity, the Sub-Total field updates, and about 25% of the time it does not. Sometimes the field is entirely empty. I need to force a refresh by exiting the layout and returning. I am the only one working on this database which at the moment is located on my laptop.
Following PhilModJunk's advice, I created a c_SubTotal field in the table (Events) on which the layout is based. I defined c_SubTotal to be a Calculation field: Sum ( Event Menus::c_LineTotal ) In testing, this has performed consistently.
Thank you both for your help!
Is likely to be 100% consistent
and with FileMaker 13, I suspect that
would also work if you gave the summary field an object name, but I prefer Sum() in these cases as I usually do not need any script at all (unless there is some other factor in play that keeps sum from updating and that can be the case sometimes.)