Re: another newbie question

Andrew,

When-New-Block-Instance fires when the input focus moves into the Block. Is your block to be populated the first navigable block? If not then the trigger won't fire until you navigate to it (you could test this by adding 'message' and 'pause' to your trigger text, however I don't believe the WNBI trigger is the answer).
When-New-Block-Instance fires at least twice on Forms startup. Once after rendering the screen, and then again after the query executes and input focus goes to the first item in the first navigable block. Using When-New-Block-Instance to execute a query should therefore result in an endless loop. Does the Form "hang"?

Try 'When-New-Form-Instance' (ensuring your block is the first navigable block), and call the built-in 'execute_query'. You don't need to wrap do_key around it unless you're customising query processing via Key-EXEQRY.

Regards,
Neville Sweet.

Andrew C. Risehnoover <qball_at_ti.com> wrote in article <3414948C.AED83480_at_ti.com>...
> In Developer2000, I am trying to get a block to populate itself
> automatically. When I create it with a button pallete and then hit
> querry, the values are populate into the block. I looked at the PL/SQL
> for this event, and all that it was was do_key('execute_query').
> So I tried to tie a trigger to new block instance so that on the loading
> of the form it would run do_key('execute_query'). However, nothing
> happens. What Gives?
>
> Also, once the table has items populated in it, how can I tell which
> ones the users are selecting? I need to grab this information to pass
> onto another module within the form. I appreciate your help.
>
> qball_at_ti.com
>
> --
> Chris Risenhoover
> Raytheon-TI Systems
> 972.927.4962
>
>
>
Received on Tue Sep 09 1997 - 00:00:00 CEST