Showing more than one row at the same time, trigger necessary?

Question

hi
I'm an absolute beginner in oracle forms, so i have a fundamental problem. i have a forms with 3 data-tables/data-blocks with following names and columns:
table "connection type": con_id, con_descr
table "connection": con_con_id (foreign key to "con_id" from "connection_typ"), sales_id (foreign key to "s_id" from "sales")
table "sales": s_id, s_descr
now i'm trying to get the following thing: when i'll execute an execute-query on "con_id" from data-block one (table "connection") i want see all records in block two (table "connection") and at the same time for each record in block two the description from "sales". so for each record in "connection" exists a record in "sales". the current problem is that i just see the "s_descr" from the selected/current record in "connection", but not all "s_descr" of every record.
i think i need a post-query-trigger but i don't know the code i need...
i hope someone understand my problem and might help me. thanks!

Answer 1

So, let me try to summarize:
Connection has a foreign key to both ConnectionType and to Sales
When you select a ConnectionType in blok1, you want to see all Connections for that type in block 2. That's a clasic Master-Detail relationship and it looks like you've got that cracked.
If you also use a Master-Detail relationship between Connection and Sales, it will make sure Oracle Forms queries the Sales block based on the value of the current record in Connection. Hence it is showing all the Sales record for the current Connection. That's always one (or none if the sales-id is optional).
You probably don't want to use a separate block for Sales with a relationship to Connection. Don't you want just a number of lookup fields. In the Connection block you also want to show the Description from the Sales table.
To accomplish that, add an extra field to the Connection block to hold the Sales Description. Then write a post-query trigger on the Connection block. That trigger will fire for each record being fetched. In that trigger you can do something like:
select description into :connection.sales_descr from sales where id=:connection.sales_id;
Alternatively you can also base the Connection block on a query in stead of directly on the Connection table. That allows you to write a Select statement that (outer) joins Connection to Sales and use that query result as the basis for the block.