Economizing T.O.'s

[jansenw]

I still somewhat new to FMPro. I hope my question makes sense.

When setting up table relationships, is it possible to economize table occurrences?

For example, if I have the following relationships:

Relationship A.

Part table --> Image table

Relationship B.

Sales table --> Part table

When creating a Layout with Relationship B, I'm not able to access the Image table defined through another relationship (in this case, Relationship A). Is the only way to do this is to add the Image table occurrence to relationship B as follows?

Sales table --> Part table --> Image table

Would adding table occurrences this way add unneeded overhead and reduce performance especially if I may need to many of this type of occurrences?

[aldipalo]

I don't believe this is true. I have several applications where each layout may have anywhere from 5 to 15 TO's and more. These applications are both standard, GUI and Data in same DB, and separation Model, Gui and Data are separate DB's and they have anywhere from 10 - 50 layouts. I have not noticed any reduction in performance.

[Oldsneekers]

Agree. The data is all the same. The creation of more relationships uses more memory (but miniscule considering the gigabytes that are hard drives these days) and no effect on performance.

[jansenw]

This is good to know.

Thanks,

- Jansen