I'm completely baffled by this.  The attached file contains two tables (Parent and Child).  Parent has three fields, Parent::Serial, Parent::DefiningProducts, and Parent::DefiningResources.  Child also has three fields, Child::Serial, Child::Products, and Child::Resources.  The relationship is a simple one:  Parent::DefiningResources = Child::Resources  AND Parent::DefiningProducts = Child::Products.

 

If you look at the portals, you will find that the relationship does not seem to be matching the expected records.

 

In particular:

• the Parent record with serial 287 is correctly matching Child records with serials 3347, 3905 and 4086, but is also incorrectly matching with serials 3906 and 4909, despite the fact that the Resources are different
• the Parent record with serial 134 is correctly matching Child records with serials 525, 1993, 3348, 3353 and 4060, but is also incorrectly matching with serial 1996 and 4088
• the Parent record with serial 305 is correctly marching Child record with serial 3888, but is also incorrectly matching with serial 4085

I'm wondering if the presence of the special characters (percents and parentheses) is somehow messing up the match?  Or is there something else going on here?

 

(The attached file is a stripped-down version of a much larger and more complicated database...  I've tried to remove everything that is extraneous to this specific issue.)

RelationshipsProblemDemo.fmp12.zip

From Help On Line:

 

A value index is created by taking each line of text (delimited by the carriage return character) and taking up to the first 100 primary character weights that all the characters in that line generate, according to the Unicode Collation Algorithm.

 

 

All your 3 products description have more than 100 chars.

Here a possible solution.

RelationshipsProblemMod.zip