Global Calculated Fields

[BeckyMN]

I'm having a tough time figuring this one out.

I have a table with three fields; two global calculated fields and one regular text. The table has only one record. The calculated fields are simply the literal strings "Yes" and "No". The regular field is only there to give the table one record.

I should also mention that the file is hosted by Filemaker Server.

When I connect remotely to the open file I expect to see the value that I entered into the regular text field along with the values of "Yes" and "No" in the globals. The value in the regular field is present but the globals don't populate. However if I create a new record the globals populate immediately. If I delete the new record the global values remain. If I close Filemaker on my PC and relaunch the globals are gone.

I understand that this is common behaviour for global text fields but I would expect that global calculated fields would calculate no matter what the situation is. In other words, they would always be populated with "Yes" and "No".

Is this normal? Can somebody explain what is going on?

Thank you,

Becky

[bcooney]

You're not alone. I noticed this behavior as well, and it caused me to avoid global calcs.

global calc thread

[comment]

I cannot test this, but I am guessing the fields were evaluated as empty before the file was served - so this is stored as the default value. Have you tried changing the calculation to unstored, then back to global?

[David Jondreau]

I think the behavior is consistent, if non-intuitive. For a global calc to evaluate, you best have a record in that table. Other than that, what issue are you having?