...someone clued me in to what I was doing wrong with my find scripting, and I was chugging right along. Then, in the database in the attached picture, I tried to create a relationship between the "Invoices" table and the "Labels" table (using the "invoice number" field).

I got an error message to the effect that there can't be more than one relationship path between two tables. Since there isn't a direct relationship path between these tables, I assume that FM is referring to the path that goes through several other tables to join these two.

So, the question is...if I want to go to the Invoices layout, and find all the related records from the Labels table, what will I have to do? FM asked me whether I wanted to create a second occurrence of the table...what happens if I do that?

Thanks...

mz

My graph

Since there is an existing relationship (through the chain), can't use use that relationship to show the labels related set?

sorry this was just confusing me when i read it... grammar error...

Since there is an existing relationship (through the chain), can't YOU use that relationship to show the labels related set?

.. but yes... why dont you just use the existing relationship?.. or if you just want to do it by invoice number, create a relationship from invoices to a new payments to.. im assuming by the invoice number... then just goto related record in that table occurance and display using the existing layout that was connected to the original labels TO...

sorry this was just confusing me when i read it... grammar error...

Okay, ee cummings.

lol... yeh, i have problems ???

Alright let have some sentences using prepositions in both Dutch/Flemish (Wims native tounge) and Danish (...mine) do not think it's as easy as it seems, if you scissors something do we stand a fair chance catching you redhanded.

Let's her something about Don Quichotte and Pancho Lanka!

--sd

but yes... why dont you just use the existing relationship?.. or if you just want to do it by invoice number, create a relationship from invoices to a new payments to.. im assuming by the invoice number... then just goto related record in that table occurance and display using the existing layout that was connected to the original labels TO...

I'm still feeling my way through this, but it doesn't seem as simple as just asking for related records. Wouldn't I have to execute a separate find/go to related records for EACH link in the relationship graph? That would be 5 or so in my example; and that sounds like more work (from both processing power and script maintenance standpoints) than should be necessary.

I did create a separate TO and that seems to have worked, but I get the impression that this is kind of a "band-aid" and I'd like to know the preferred way to do this before I march off and replicate it 100 times.

Thanks...

mz

... no you would NOT have to do a find / go to related records in each link... you would just do it once from your original TO directly to your Labels TO...

lol yeh soren i know, im actually really impressed with you guys, its just that your english is so good sometimes that i forget that your dutch / danish etc.

genx

lol yeh soren i know, im actually really impressed with you guys, its just that your english is so good sometimes that i forget that your dutch / danish etc.

genx

Speaking of English, that would be "that i forget that you're ..."

With capital "I".

that i forget that your dutch / danish etc.

Not all Dutch speaking people are Dutch either...

bah... shhh, i get it, i'm picky... just shhhh...

oh well all in good fun i suppose, i can be annoying sometimes but still... sigh

genx

and yes, i stand corrected about everything... pardon the dutch / danish assumption...

genx

There isn't one set good way to do this, it really depends on the solution.

With your original graph, a single GTRR to labels would give you the related lables, provided that all relationships throughout the chain are valid and populated with records.

Creating a new labels TO like you did works too. Now the "context" comes into play. Layouts are based on TOs so whenever you want to show data in a layout and perform actions on it, you need to think what labels TO you'll want that on, and how you can get to what data from there.