Re: FORMS_DDL('rollback') - does it makes sense?
From: Tiago Rocha <please.see.link.at.signature.for.email.address_at_zaz.com.br>
Date: Fri, 19 Mar 2004 09:21:15 -0300
Message-ID: <papl50l57ogei0k8tp51utqjd10sfnsf6k_at_4ax.com>
Date: Fri, 19 Mar 2004 09:21:15 -0300
Message-ID: <papl50l57ogei0k8tp51utqjd10sfnsf6k_at_4ax.com>
[Quoted] On 19 Mar 2004 03:31:22 -0800, rolf.unger_at_ctilabs.de (Rolf Unger) wrote:
>Hi,
>
>I want to do a rollback of my
>
> update table_b set col_a=2 where col_b = :BLOCK_A.col_b;
>
>that I have executed in a "WHEN-BUTTON-PRESSED" trigger.
>
>If I simply do the natural approach and use a "ROLLBACK"
>inside the trigger code, FORMS converts it to the built-in
>"Clear_Form" and all my blocks are empty.
>That's not what I want!
You can tell forms that these records aren't new, so forms won't issue an "insert" or "update".
Set_Record_Property( block_name, 'QUERY_STATUS' ) will do this.
hth
-- Tiago Rocha Recife - Brasil www.diariodastrilhas.cjb.netReceived on Fri Mar 19 2004 - 13:21:15 CET