Re: Forms 5: Populating Intersection Tables

Hi Brian,

Why don't you defer creation of the intersecting row until the keys exist? You could simply capture the fact that a row was clicked and then during commit processing create the required intersecting row. For example, set a non-display table item of varchar(1) to 'Y' when the row is clicked, and then in a Post-Insert trigger if the item = 'Y' then insert your intersecting row.
You might also consider using a displayed checkbox, so that the user could change their mind about the intersection prior to commit.

Brian Neary wrote in message ...
>Forms 5.0:
>
>How can I create rows for my intersection table before committing to the
>database.
>
>I have two tables in my form, Table1 and Table2.
>As I add Items in Table1 and Table2 I want to create an intersection
between
>rows in Table1 and Table2 . The idea I had was to capture a double click
on
>Table1 and create a row in my intersection table(Table 3) between
>Table1.(clicked row) and the current row in Table2.
>The problem is, if any of the rows have not been committed to the database
I
>have no key to write into my intersection table.
>
>In general, I'm trying to populate an intersection table with foreign keys
>before the keys are available.
>
>I'm looking for ideas as to how other developers have handle this
situation.
>
>Thanks for any help, Brian
Received on Mon Mar 13 2000 - 04:53:20 CET