I have three tables

tableA

tableB (master join keyID)

tableC

C is relate to B (b keyID) which holds a foreign key to A.

while in C I would like to see relationship to A via B, but after record creation (via server, commit record, all indexed) the relationship will not display untill all files are closed and reopened?

is this how it should be?

If I but the A_key rigt in C, no problem , but what a drag.

I have three tables

tableA

tableB (master join keyID)

tableC

C is relate to B (b keyID) which holds a foreign key to A.

while in C I would like to see relationship to A via B, but after record creation (via server, commit record, all indexed) the relationship will not display untill all files are closed and reopened?

is this how it should be?

If I but the A_key rigt in C, no problem , but what a drag.

I have three tables

tableA

tableB (master join keyID)

tableC

C is relate to B (b keyID) which holds a foreign key to A.

while in C I would like to see relationship to A via B, but after record creation (via server, commit record, all indexed) the relationship will not display untill all files are closed and reopened?

is this how it should be?

If I but the A_key rigt in C, no problem , but what a drag.

Not sure if this is what you are looking for but if you want to see the data linked to a specifically, you could create an unstored calculation to "bring over" the A data into B so that it can then be displayed in C via its relationship to B.

Not sure if this is what you are looking for but if you want to see the data linked to a specifically, you could create an unstored calculation to "bring over" the A data into B so that it can then be displayed in C via its relationship to B.

Not sure if this is what you are looking for but if you want to see the data linked to a specifically, you could create an unstored calculation to "bring over" the A data into B so that it can then be displayed in C via its relationship to B.