which table occurrence to choose globals

[Charity]

This is a general question but not hypothetical.

I have global dates (start and end) in a regular data table (Accounts) because they are used in relationships. When need arises to insert one of these globals into a calculation, does it matter which table occurrence of Accounts is chosen?

It seems no because FM sees them from anywhere but knowing for sure would be great. With regular fields it seems important to pay attention to the lines back through things and use one that is not only related but the best choice; properly filtered, direct route. So, if in a related table anyway, does it help to choose that related Accounts to get the global field or does it simply not matter at all? Or would I visually try to grab the one closest sitting in the graph?

btw just because I am working on this issue this moment does not mean I have not researched this subject beforehand. There are no posts on this forum or filemaker forum which mentions this so it is probably dumb to even bring up. regardless...it picks at me until I know. also in testing no difference is easily observed.

[comment]

It doesn't matter. However, good practice (IMHO) would dictate selecting the "base TO" - if only because it's the one least likely to get deleted when the file is tweaked.

[Charity]

OMG. Good point. I never ever would have thought of that. And I will relax with globals now - FM is time space continuum and globals fold space negating distance/position. That will be easy for me to remember!