Under storage options for the calculation field click do not store - recalculate as needed.
The calculation should not need to be unstored. That is needed if the calculation uses a Get function, but changes to a field referenced in the calculation should cause the calculation to update automatically without having to make the field an unstored calculation.
Perhaps you have defined a number or text field with an auto-enter calculation? There are cases where that won't update automatically and the solution is often to select the field in Manage | Database | Fields and change the field type to calculation. The auto-enter calculation, BTW, will be preserved when you make this change.
Excellent thank you. The field was a text field, once I changed it to a Calculation it now works the way I wanted.
The last time I used FM it was version 7 so I am a tad rusty!
One happy camper :)
I assumed it was already a calculation field, because of the title. How do you force a calculation field to calculate.
Thanks for this post it is interesting,
But all of this is a tad bit too much for me, how can you force Filemaker to calculate an Excel file, since the first row or record of any Excel file is usually the Title to the Column or Field? were as in Filemaker the Field definition is seperate from the records or row occurances.
...how can you force Filemaker to calculate an Excel file, since the first row or record of any Excel file is usually the Title to the Column or Field? were as in Filemaker the Field definition is seperate from the records or row occurances.
There isn't any way to force an excel file to calculate in FileMaker.
That really wasn't what the poster asked. They were comparing how calculations evaluate in Excel to how they evaluate (for an auto-entered calculation as it turns out) in FileMaker.
Apologies for confusing folks.
I hadn't realised that a field type could be a "Calculation" as I had created a "Text" field and then via options created a Calculation for the field, thinking it would then do the calculation.
Once S Chamblee had explained that I needed to use a "calculation" field type it all worked exactly as I wanted it to.