The DB can be seen as a Flower Shop situation using only 2 tables :
T_bouquets, main table which records contain
a) a name bouquet_Name
b) six flower fields ID_flowerN (N from 0 to 5) containing
an optional reference to a flower in T_flower_list.
T_flower_list , contains the names flower_name of available flowers.
So each main table record defines a bouquet’s name and up to 6 references to the selected flowers. And one can imagine all kinds of bouquets : undefined bouquet with no flower, some bouquets might have only one type of flower, other bouquets could combine flowers randomly, etc…
I have created a few queries displaying the ID-flower references in T_bouquets (with the exception of ID_flower0 which can be displayed by name through the relation). It works, but the reference numbers in the query results have no meaning to the end user florist, who wants to read the flower names!
HOW TO establish the needed relations between the two tables and set up the SQL to display the flower names in place of the flower reference ID number ? It needs to change my “OK_by_ID…” queries In the example to some new “OK_BY-NAME…” queries ! I believe that it is possible in LibO.
Maybe that he solution needs a different table approach, or it might have something to do with the AskLibO discussion here Grouping in base report based on multiple fields with common entries ?