Re: Oracle Forms 3.0: Referencing Fields

[Quoted] On Tue, 3 Oct 2000 20:02:52 -0700, "Matt B." <mcb_at_fightspam.sd.znet.com> wrote:

>"Dons" <m.v.vandonselaar_at_donotspam.kpn.com> wrote in message
>news:en3ktsg288sv401g5g5rqqu41pnr4q5nch_at_4ax.com...
>> Hi,
>>
>> I'm working on a forms30 form and I have problems referencing fields
>> in PL/SQL. It seems sometimes referencing a field returns no value.
>> This happens if I have called another form via CALL_QUERY and press
>> the exit key so I return to the original form.
>>
>> Hopefully anyone can explain what's the problem
>>
>> Greetings,
>>
>> Martin
>>
>> PS. I Know I should quit using this old stuff, tell my boss ;-)
>
>How are you referencing the field? Can you give an example?

Procedure set_visible_page is

   begin

     if name_in('b_hrk.soort_interface') = 'JP' then
       show_interf_data('6');
     elsif :b_hrk.soort_interface = 'FAC' then
       show_interf_data('7');
     elsif :b_hrk.soort_interface = 'AANVRAAG'
       OR :b_hrk.soort_interface = 'ONTV' then
       show_interf_data('8');
     elsif :b_hrk.soort_interface = 'PROJECT' then
       show_interf_data('9');
     else
       hide_interf_data;  
     end if;

   Procedure show_interf_data (p_page IN varchar2) is    begin

     if p_page <> 6 then 
       hide_page(6);
     end if;
     if p_page <> 7 then 
       hide_page(7);
     end if;
     if p_page <> 8 then 
       hide_page(8);
     end if;
     if p_page <> 9 then 
       hide_page(9);
     end if;
     show_page(p_page);

   Procedure hide_interf_data is
   begin

     hide_page(6);
     hide_page(7);
     hide_page(8);
     hide_page(9);

As you can see I tried name_in als well as the 'normal' referencing. Both do not seem to work. I'm sure this procedure runs (at the rigth moment) because I tested this in debug mode. Normally it runs fine (It is called from a PRE_RECORD_TRIGGER and ON-VALIDATE-FIELD on b_hrk.soort_interface). However it does not if called from a on-new-field-instance or in the situation in my original post (even when the PRE_RECORD_TRIGGER fires). I'm out of options but I migth be missing the obvious? Maybe the problem is something else?

Greetz,

Martin Received on Wed Oct 04 2000 - 16:30:04 CEST