Re: Difficult Forms 4.5 trigger question

The solution with a timer is very strange and certainly not the best. Try rather with trigger WHEN-NEW-FORM-INSTANCE. With this trigger, you can use all restricted procedures, what you can't do with PRE-FORM.

Steve Cosner wrote:
>
> Walter,
>
> Use a timer. In your master block's when-validate-record or some
> other appropriate trigger, start a timer that expires in 1
> millisecond. In the when-timer-expired trigger, you can go_block to
> your detail blocks and ensure that records are created there as well.
>
> The main thing to be careful of here is that you need to do your
> commit from a timer that expires AFTER the first one (I use 100
> milliseconds). This allows the first timer to do all its work, before
> a commit is done.
>
> Hope this helps.
> Steve Cosner
>
> And PLEASE use comp.databases.oracle.tools for Forms questions.
>
> In article <55t1nl$noh_at_arktur.rz.uni-ulm.de>,
> Walter Zimmer <walter.zimmer_at_rz.uni-ulm.de> wrote:
> >Hi !
> >
> >I have a block with a detail block which in turn has another detail block.
> >I want to make sure that every time a new master block is inserted, every
> >detail block is inserted, too. I can do this by hand by entering
> >values in the detail blocks, so they become 'INSERT' status and get
> >automatically into the database with the next commit_form.
> >
> >But, if I dont enter values into the detail blocks, they wont get inserted
> >and the next query returns: No DATA FOUND for the detail block.
> >
> >I played with some triggers, but didn't find any which allow me to
> >mark the detail blocks as 'INSERT' because even in the PRE_FORM trigger
> >I cant execute GO_BLOCK.
> >
> >So, how do I populate the detail blocks at form startup when the only
> >navigeted block is the master block ???
Received on Sun Nov 10 1996 - 00:00:00 CET