Hello,

This is probably a newbie question that I should know the answer to!

I have a calculated field that is serving as a match field for two tables. This match field is:

Subject_ID & Initials & Visit_Date

(Side note: In both tables, the Initials field is pulling from a different (third) table.)

The match does not seem to be working - in the portal, I am getting data from the related table, but too much of it, as though the match field is not working properly. It seems to be matching only on the Subject_ID and not including Initials nor Visit_Date.

Could the problem be that Initials is a related field to begin with, or perhaps it is a problem with indexing? Any advice would be much appreciated, I feel like I am going crazy and should know why this is not working!

Regards,

julia

A 'child' table's match field must be indexed in order for a relationship to work. A calculation field involving a related field cannot be indexed, therefore it cannot be used as a match field on the 'child' side.

Is there any chance you can use an auto-entered calculation or a lookup for the field instead? Also, you do not need to make a concatenated field for a relationship anymore; you can make a multi-criteria relationship where

T1::Subject_ID = T2::SubjectID AND

T1::Visit_Date = T2::Visit_Date AND

T1::Initials = T2::Initials

assuming that Initials can be indexed in at least one of the two tables.