Re: Oracle Forms: Need advice

From: Dave Williams <davetati_at_dsli.com>
Date: Fri, 8 Aug 2003 13:39:07 -0400
Message-ID: <yAGdncCJIfzaeq6iXTWJig_at_dsli.com>


Jeff,

Ok, that is what I was thinking of doing. I think I'll do this since it will be easier to control.

Cheers.
"Jeff" <jeff_at_work.com> wrote in message news:bgtfql$bmb$1_at_cronkite.cc.uga.edu...
> In article <JroYa.676063$Vi5.15958416_at_news1.calgary.shaw.ca>, "Maximus"
<qweqwe_at_qwqwewq.com> wrote:
> >"Dave Williams" <davetati_at_dsli.com> wrote in message
> >news:YvucnQm_Dt6cm6yiU-KYgg_at_dsli.com...
> >> All,
> >>
> >> Need some advice on what the best way to handle the following situation
> >is.
> >>
> >> I have a form that is based upon a DB table. There are about 4 columns
> >that
> >> are id's and link to other tables. I have a post_query trigger that
> >obtains
> >> the data from the relevant tables and puts them into text fields on the
> >> form. So, the id fields are never displayed. If a query is run and I
> >then
> >> elect to close the form it asks if I want to save the data, assuming
here
> >> that since the data was loaded into text fields Oracle Forms is now
> >thinking
> >> that the data has been modified.
> >>
> >> What I have done in the past is to use the set_record_property in the
> >> post_query table.
> >>
> >> Is there a better way of handling this ?
> >
> >If you modify item values in a block programatically or interactively
after
> >a query, such as during a post-query trigger, you will mark the
block/record
> >status as 'changed' and you will be prompted to save those changes upon
> >exit, that is the way block functionality works. If you want to simply
> >display values in a form, say programatically from a post-query trigger,
use
> >'display' items instead of 'text' items, this doesn't affect the status
of
> >the block if they are modified.

>

> Alternatively, if for some reason you don't want to use display items, you
> could move these never-updated text items to a non-database control block.
Received on Fri Aug 08 2003 - 19:39:07 CEST

Original text of this message