relating to a calc field

[Aussie John]

Sometime if I relate to a calculation field the relationship works but at other times it doesn't. I think it is when the field is unstored, but if I try to change the store option FM wont let me (saying it references a related file, or unstored calculation) .

Is there a method to get this to work? thanks

[comment]

Unstored (or otherwise non-indexable) fields cannot be used on the "other" side of the relationship.

[Aussie John]

Thanks - is there a way to stop the calculation being unstored?

[Søren Dyhr]

By Ugo'ing .... http://fmforums.com/forum/showpost.php?post/153242/

--sd

[comment]

is there a way to stop the calculation being unstored?

If the calculation references a global or a related field, then no - it is forced to be unstored. Otherwise it wouldn't update following modification of the referenced values.

There are probably other ways to approach the underlying problem - but you haven't told us what that is. One of these ways is the "Ugo method" - but IMHO that should be used as the last resort, not first.

[Aussie John]

A little involved - use a table (I call it the "view" table) with a single record and a portal on the layout. The fields of the view table use value lists sourced from the multiple related fields. I can then select a value list item and the portal quickly changes to see a different set of data.

My issue is the related table also relates to another table for some of its info and I would like the view table to be able to filter that too. I tried a calculation to mimic the field of the second related table and this is where the unstored problems arise.

[comment]

the related table also relates to another table for some of its info

That's a rather general description. Perhaps you can place a TO of the "another" table in-between the "view" table and the portal table, to act as a filter.