Ok. In < 7 data flowed only one way. And the left side could be anything but the right must be indexable. In 7, data flows both ways. But if the left is a global, how can it? Can someone just help me clear my thinking on this concept? Isn't there still a left and right side? Or is that the old entity-based thinking.

It's probably alot to ask but my mind sits and spins with the inconsistency of it. I stare at my multiple TOGs in awe and no, I haven't tried flowing through a global or unstored calc because I just don't see how it can.

Old thinking sure dies hard. My biggest challenge in 7 is unlearning ... more than learning.

LaRetta

If one side is a global field the information flows only one way even in 7. Take a closer look at the relationship diagram when connecting a global field to an indexed field in another table, the lines end differently indicating a one way relationship.

Hi fmsavey!

And so they do - the end IS different! My eyes aren't very good! That certainly helps me track the flow through my spider-webs (smile). I'm glad I haven't tried flowing through one yet and that answers many questions for me. Thank you so much.

LaRetta

There are several reasons the TOG might indicate a one-to-many instead of a many-to-many (if the key on one side is validated to be unique, if the key is an auto-entered serial#, or if it is unstored like with a global). This does not mean the relationship is one way, it indicates a one-to-many. From the 'many' side, you only see one related record on the 'one' side.

LaRetta, you should try to distinguish on your graph, those TOGs that are part of the data flow, vs. those TOGs that are part of the interface. Usually globals are only used as part of the keys in interface relationships. This way your data relationships will show you how the data flows between tables (like with lookups.)

Oops, there is a slightly different indicator for the 'one' side of if it is unstored. Missed that.