Re: changing blocks programatically in Forms

From: George Buckner <synthesys_at_mindspring.com>
Date: Fri, 27 Sep 2002 03:16:49 GMT
Message-ID: <3d93cc9f.1772318_at_news.mindspring.com>


Hi Joost:

>I remember having the same problem and fixing it by setting
>system.form_status to 'QUERY' before executing the 'go_block'. Of course you
>can only do this if no changes have been made, otherwise you will lose then.
>I'd suggest you experiment with
>IF :System.Block_Status = 'CHANGED'
> THEN Commit_Form;
>END IF;
>:system.block_status := 'QUERY';
>go_block('your_block_name');
>Does this help?

[Quoted] You must be talking about set_record_status. System.form/block_status are [Quoted] read only. Once I changed set_record_status (to new or query) it worked fine. In fact I discovered where I had put a value in a field in a trigger. Once I put that value somewhere outside of the data block I didn't even have to use set_record_status. That answered my question as to why it thought there were changes to post to start with.

Thanks.

George Buckner Received on Fri Sep 27 2002 - 05:16:49 CEST

Original text of this message