Re: Strange Forms4.5 error

From: Nigel J Underwood <Nigel_at_vnvi.demon.co.uk>
Date: 1995/07/19
Message-ID: <806190651snz_at_vnvi.demon.co.uk>#1/1


In article <3uja2m$1nd_at_big.aa.net> fern_at_big.aa.net "Fernando Luna" writes:

> Rob Zoeteweij (Rob.Zoeteweij_at_inter.nl.net) wrote:
> : When running the next procedure from the PRE-FORM trigger :
 

> : procedure init_params is
> : begin
> : :GLOBAL.first_block := get_form_property(:SYSTEM.current_form,

                                         FIRST_NAVIGATION_BLOCK);

> : :GLOBAL.first_block_item :=
> : get_block_property(:GLOBAL.first_block,FIRST_ITEM);
> : end;
 

> : Runform will give me "FRM-40738 : Argument 2 to builtin
> : GET_BLOCK_PROPERTY cannot be null"
>
> Hmmmm.... Have you tried changing the PRE-FORM trigger to a
> WHEN-NEW-FORM-INSTANCE trigger? I've found, especially in Forms 4.0,
> though I realize we're talking 4.5 here, that sometimes a problem that
> presents itself in PRE-FORM goes away in WHEN-NEW-FORM-INSTANCE...
>
> Hope that helps...
>

I suspect the problem you are getting is due to the fact that you are using the package procedure get_block_property in a pre-form trigger. When the pre-form trigger fires on a form, the navigation at that point is before form level and therefore it could be said that the form hasn't actually started. As a result, requesting block properties could be out of the scope of the form at that time. Try changing the pre-form to a key-startup and see what happens.....

-- 
Nigel J Underwood

EMail : Nigel_at_vnvi.demon.co.uk
Received on Wed Jul 19 1995 - 00:00:00 CEST

Original text of this message