Hi ! Sorry for my bad English

Lets say we have 3 tables A, B, C

Table A has 10 Global fields (Gkey1, Gkey2, Gkey3 e.t.c)

Table B also has 10 Global fields (Gkey1, Gkey2, Gkey3 e.t.c)

Table C also has 10 Global fields (Gkey1, Gkey2, Gkey3 e.t.c)

The Global Fields in every case is Keys to get images from a FMPro photo album

I manage the Global fields from the Table A . I put the data in the Key fields via script and the images come via a portal.

Everything work perfect.

The purpose here is when I fill with data the Table A (Gkey1, Gkey2, Gkey3 e.t.c) Keys

the corresponded fields (Gkey1, Gkey2, Gkey3 e.t.c) Keys from Table B & from Table C also filled with the same data.

So when I go to the Table B or Table C I expect to see the same Images in the Table B or Table C portals.

How can I inform the corresponded fields (Gkey1, Gkey2, Gkey3 e.t.c) in the Table B or Table C

In every case the rule is Table

A::Gkey1 = Table B::Gkey1 = Table C::Gkey1

A::Gkey2 = Table B::Gkey2 = Table C::Gkey2........

Anyone please??

George

Did you try using a global calculation field for Table B::GKeyX that just sets the value to A::GKeyX?

Does't work...

sorry

How about the same script that sets A::GKeyX also sets Table B::GKeyX and Table C::GKeyX?

That is possible in FM7, since you don't need a relationship to access globals.

It works this way... but I want to avoid to many steps in the script.

I have 10 set field for one table. If want to expand the solution to 6 or 10 tables I have to write 60 or 100 set field steps. (not good performance)!

Well, another possibility, if A, B, and C are not currently related to one another:

Make a new table, Z, that A, B, C are each related to with a cross-product join (x).

Table Z contains the GKeyX globals, and is related to the table holding the graphics.

Then on each layout, you can put the image fields from the graphic table into the portal, showing them from multiple tables away.

You could do the same if A, B, C are inter-related, but then you'll need to add multiple occurrences of Z to the relationship graph, so no cycles exist.