Sorry initially included image is still in Japanese, here is English version. Tank you.
Table 1 is what is commonly called a "cross tab" report. There are many posts on that subject in this forum.
Table 1 might be a table with one record for each analysis ID value with portals that arrange the data from different related records from table 2 into columns. This is often done with a list view layout where the columns of data are created with one row portals. Different relationships or different portal filters can pull records for "item 1" into the first such one row portal and a different filter or relationship pulls data for "item 2" into the next column.
The columns can also be produced with calculation fields using ExecuteSQL(), but you have indicated that you did not want to use that option.
PhilModjunk, Thank you for your reply.
This type of table is called “cross tab” report. That information IS quite a big help, since I did not know how it’s called in English. I will now on search with the topic. Many Many thanks.
Here’s my progress report;
I have been trying for some time, but for the time being, without any success as far as relationship part is concerned.
So, I, tentatively, tackled it, from a opposite direction.
As you mentioned, I prepared some repetition fields with ExecuteSQL() functions., and managed to mimic the table-1 from table-2 records. For a data editing issue on the table-1, I placed a button containing a script for calling data entry layout. This is in a roundabout way from what I am expecting, but still it is functional.
I will start looking into Cross Tab Report issues, your comment leads me to it. Thanks again.
Yoshio Ogata, Kyoto Japan.
Thanks for Phil's advice, I somehow managed to implement the Relational parts.
I found the attached image has logical errors, I will post a collected image. Sorry for messing up this board, and Thanks again.
Yoshio, from kyoto Japan