Help me resolve my terrible relationship with Ref columns 😩

[TedM]

I know this should be easy but for some reason I keep messing it up!

My scenario:
Two tables - Quotes and RAMS both with a single row per record.  A Quote would usually be associated with only one RAMS .... but occasionally there might be two or three.

A Quote is created first and has, amongst other fields a Quote No. field that is Text - this is unique to each row:

The Quotes table also has the virtual Related RAMSs field:

The RAMS table also has a Quote No. field which is a Ref with the Quotes table as the source:

If I create a RAMS row with the same Quote No. as a row in the Quotes table - why does the Related RAMSs field stay empty?

[Trevwiller]

so the Quote table is our parent and RAMs is our child. With the RAMs rows for the Quote No. We need to hold the key value from the Quote Table. This makes it a child of the table.

Are quotes and RAMS made in this same app. If they are not check your setting for performance and uncheck the options quick sync, and delta sync. These prevent cross app communication.

[JMPeterson]

Just thinking through how I would troubleshoot this; when you add new RAMs, can you verify that the unique ID of the assigned Quote No. is being populated in the field and not the text value of the column Quote No? If you create a FILTER/SELECT statement where [Quote No.]=[_THISROW].[Quote No.], do you see the expected values?

[TedM]

All sorted now thanks for the pointers.