Naming conventions: unstored calc made of summary fields

[Ignasi Alemany]

I have a calculation field with "summaryField2 / summaryField"

According to the naming standards it should be named after the prefix "unstored" however the field function is clearly a "summary" and I'm tempted to prefix it with "summary".

How would you name it according to the filemakerstandards.org naming conventions?

[Jeremy Bante]

Either is fine. Unstored calculation fields merit their own special prefix because they have performance consequences that developers need to be conscious of whenever using them. Summary fields have similar consequences, so the "summary" prefix works just as well for the same effect. Use whichever prefix you think is the most informative.