Unstored Calculation

[Slobey]

I have a question about relating calc fields. I noticed that if I try to establish a relationship using an unstored calc, it won't work. (if I try GTRR it tells me the relationship is invalid) but if I establish the relationship using a lookup or auto enter calc and then change the field to an unstored, it works. Why is this? and how unstable is it once it is unstored?

I appreciate any input

Mike

[comment]

It is not a question of stability. A relationship needs an indexed field on the "other" side (in your case, the side that GTRR needs to go to). The results of an unstored calculation cannot be indexed, because they are not kept. The only thing that is kept is the formula - and every time a result is needed, Filemaker looks at the formula and calculates again.

A lookup/auto-enter is stored, but Filemaker will not recalculate it automatically when the source data is modified, except under very specific conditions.

[Earthling]

As far as I remember (and you can try this out to see if it works) you can have an additional calculation field that = your unstored calculation and make it an indexed value as long as it is in the same table

[Ender]

As far as I remember (and you can try this out to see if it works) you can have an additional calculation field that = your unstored calculation and make it an indexed value as long as it is in the same table

Well, a calc based on an unstored calc will be necessarily unstored itself.

[Earthling]

Yep you are right of course and I should have checked myself before irresponsibly posting bad information....thanks for the correction ???