Re: Forms 4 - 'nothing to commit'

jonda_at_ifi.uio.no writes:

>The worst is, that a PL/SQL "commit" statement in a trigger or PL/SQL
>program unit (within the form) is interpreted as a "commit_form"
>statement.
>

Don't entirely agree - though Forms is taking it as a commit form, (shown by the warning that there's nothing to commit) it does seem to commit my own updates - i.e. within the trigger, update the table from the item's modified contents, then commit.

> (as a dummy table and a invisible dummy field that you
>change immediately before a commit, just to cheat Forms to commit the
>inserts/updates you really want to commit...), you have lost the
>freedom of the GUI; i.e. you can't access the fields/items in a random
>way...
>
>

Yes, this is a crazy state of affairs. While it's easy to get a good looking screen or two up, basic application functions are difficult.

          Gary John Walker     gjwalker_at_gjw1992.demon.co.uk
          -------------------------------------------------