>I have found a strange problem with GRIDs and SET RELATIONs.
>
>Suppose I have a table with fields KEY_A and KEY_B, which are foreign keys in TABLE_A and TABLE_B respectively. I want to set up a grid showing KEY_A, TABLE_A.NAME_A, KEY_B, TABLE_B.NAME_B, and be able to add new records with a command button.
>
>I set all this up in the data environment of the screen, but when I add records, I get strange behaviors: either a RECORD OUT OF RANGE error message shows up, or wrong NAME_A o NAME_B values appear.
>
>If I set up a grid with only ONE relation, the grid works fine, but when I try to work with two or more related tables, I cannot get it to work.
>
>Does someone know what this is all about? Is there a patch, a fix or a workaround for the problem?
>
>Thanks!

The generic rule is following: it's very easy to build simple temp relartionship and use it for grid, but the more complicated your interface will become the more troubles you will get. You definitely should remove temp relationships and use parameterized views or read/write cursor as grid recordsource.