What storage options are specified for the two RMK fields? It would appear that one of them is either unstored or global.
On which occurrence is the layout you've shown based?
The field RMK in the TransOE table is text (loaded from a script)
the Field RMK in the RMK table is calulated unstored.
Since "The report uses the TransOE table,"
this will not work the field has to be a stored, indexed field in order for the relationship to work. The other RMK field could be global or unstored but not the one from the related table.
You'll need to come up with an alternate approach to work around this.
Sometimes you can set up a script trigger to calculate the needed value and store it in a simple number or text field. In other cases, you might be able to set up a filtered portal where the portal filter expression can use the unstored field that won't work in the relationship itself.
Ok, let me do some changing .. thanks