I am having a problem with a relationship between two files.

In doc A I have a field with name and an identifier with the value "U".

In doc B I have a list of values by persons, plus a calculated field (ID) marking the unique values for each person (using a self-join relationship), making a list of unique values for each person in the table by searching on person name and ID=U. Follow me?

Now: In doc A I would like to have a portal, displaying this list of unique values for each person, meaning that when I am on John Doe's record in doc A, I would get a list of the unique values related to him in doc B.

To accomplish this I made the relationship: person = person AND Identifier (U) = ID (which is the calculated field, giving U if a unique value and D if not).

This relationship does not work, giving zero values. If I relate to a fixed field in doc B, where I manually have entered the value U it works.

Is it not possible to make a relationship using a calculated value?

In doc B I have a list of values by persons, plus a calculated field (ID) marking the unique values for each person (using a self-join relationship), making a list of unique values for each person in the table by searching on person name and ID=U. Follow me?

No.

Is it not possible to make a relationship using a calculated value?

The matchfield on the "other" side of the relationship must be indexable. It seems you are trying to use an unstored calculation for this, and that won't work.

Hmm. I suspected that this was the problem: relating to an unindexed field. But then I would have to change the way I mark up the unique values, because as done now, it cannot be indexed.

- Any suggestions?

It's difficult to make suggestions without understanding the problem. I gather you want a portal of unique values only - there are methods to achieve that, for example: make your calculation in the child table =

Case ( ChildID = SelfJoin::ChildID ; ChildID )

then join a third TO of child to the first one, matching the calculation field to the ChildID, and point the portal to it.

A simpler method would have a real table for the tracked values attached to the other side of child.