is it set to recalculate every time and not store results?
The box is checked "Do not Store Calculation results-recalculate when needed" under the options. I do not see any setting like that for the summary fields.
The weird thing is, it does not happen every time.
The things i added since this started was
1. A LOCK field that does which includes an trigger script when entering the record to lock certain fields but this does not include any of these calculation or summary field that are having the issue.
And 2. a script to add records in another layout, but the current layout has a portal to that layout.
Are you displaying a summary field from a related table? That method often results in a field that doesn't update as smoothly as we'd like. If so, you can get the same results without a refresh issue if you define a calculation with a Sum() or other aggregate function to add up (or perform other aggregate functions on) the values from the related table.
Yes, I am displaying summary fields from a related table. I will try the SUM() instead or summary fields.
Any ideas on the calculation in the same layout? These calculation are linked through a portal with the same layout. So I guess it has a relationship with itself.
How is the data being changed? By you on this layout, by you on another layout or by other users sharing the database?
The calculation fields being changed by myself and others in the same layout. But, its in a portal showing the information from the same layout. Does that make sense?
The summary fields are being changed by myself and other from another layout.
To explain in more detail...
Are you looking at a field and expecting it to update when another user on the network edits data?
Does anyone know what may be causing this? I know more information may be needed for you to help but, i have know idea where to start without describing every function in my data base.
There are several scenarios in which this may happen. Basically, Filemaker refreshes the screen only when it thinks it's needed - and sometimes it isn't aware of all dependencies. The most common cases: a relationship that depends on the results of another relationship, and using related summary fields.
Adding an arbitrary reference to a calculation can provide a solution in some cases . In others, there is no recourse except calling Refresh Window explicitly.