chain of related info!

[arlune]

hello,

I have the following problem:

each record of my database ITEMS.fp7 (synonym) can have many related items (records) in same database, input via portal to another database related_ITEMS.fp7

for example: separate records in ITEMS with name:

colors

kleuren

rainbow

prisma

RGB...

The meanings are

[Ugo DI LUCA]

Hi,

If Kleuren is related to Colors, and Rainbow is related to Kleuren, then Rainbow is related to Colors, and so would be RGB.

So the chain starts from the first Parent, Colors.

So, what do you want exacly ?

A way to identify each item of a chain based on a key from the chain ?

[arlune]

I understand that all these items are related to each other so it can't be hard to display them in a field or in a portal on each record of the items.

record Colors will have a field (or portal) with all the items related showing, "Kleuren, Rainbow, RGB"

record Kleuren, field which displays "Colors, Rainbow, RGB"

record Rainbow, field which displays "Kleuren, Colors, RGB"

...

I hope this explanation makes it easier to understand,

thanks, Lea

[Ugo DI LUCA]

You just need a multiline key field for each, with the IDs of these synonim separated by a carriage return.

Then create a relationship from the word ID and its MultilineID Key.

Sya Color is ID001, Kleuren is ID007, RGB is ID013 and Rainbow is ID050

Then Color (ID001) would have a MultiLineID of ;

ID007

ID013

ID050

A portal based on this relationship should then display those related words.

[arlune]

Your explanation sounds like what I have tried to do in related_ITEMS.fp7 not in ITEMS.fp7, how do you place all the different items in the MultilineID key? (cfr. chain, only relating one ITEM / record)

My problem is that I can't seem to get all these ID's in one multiline key field because they are in different records

Record with Kleuren related to Colors, record with Colors related to Rainbow, record with Rainbow related to RGB, how do I get the ID of RGB, Rainbow in the first record? (without manual inputs)

thanks again,

Lea

[Ugo DI LUCA]

Hi,

I'd use a layout with

- a 'Clairvoyance' Portal filtering all possible values,

- one tempIDField (global)

- a relationship Table1:tempField<-->Table1:ID

- a button in the Clairvoyance Portal with a script attached.

SetField[Table1:tempIDField;Clairvoyance:ID]

SetField[Table1:MultiLineID; Table1:MultiLineID & Case(not PatternCount(Table1:MultiLineID; tempIDField),"

[arlune]

hello,

thanks for the information but I'm not sure if this is the right solution for my problem, I don't want to use buttons with scripts, I'm looking for a solution that is automatically conceived, I've included a scheme in a word document with a short description which I think is more clear,

greetings, lea

DB_ITEMS.txt

[Ugo DI LUCA]

Hi,

Seems to me involving only pure relationship design in this instance would just lead your db to be un-usable.

The ValueListItems can be used in this instance, but then you'd deal with so many related unstored calculations, that the time to process any search will dramatically increase.

Just in case, take a look to the MultiLevel sampler.

It was made with 5.5, more likely adressing Tree-Like systems, but it might do what you're looking for too and has no script.