I'm trying to find out why switching one of my key fields from a static text field to a calculation field is causing the calculation fields of the parent table not to work. Initially, the static text field was manipulated by a script, and the parent table had no problem calculating other fields based on this relationship. Now the parent table's calc fields provide me with nothing. There's something about the field now being a calc field that's breaking up the relationship. Any ideas?

If the calculation is unstored, it cannot be used for relationship (on the child side).

That's unfortunate. I guess I could change the field back to a text field, and create another calc field that could serve as a temporary bucket for the calculations. Then I could run a script to update the text field used in the relationship. Something like:

Loop

Set Field[tableX::text field; tableX::Calc field]

Go to Record/Request/Page [Next; Exit after last]

End Loop

Hard to advise with so little information about the problem.