stack dump Forms 4.5, Oracle 7.3. VMS 7.2 and globals

Hello,

[Quoted] This all happens with an oracle 7.3 database, forms 4.5 on a VMS platform.

The steps to force a stack dump are the following:

Step one:
I Query on an item in form 1.

Step two:
I query on the same item in form 2 and get an error: FRM-40735: pre query trigger raised unhandled exception

The trigger:
default_value ('','GLOBAL.form2_ITEM_NO'); if :global.item_no is not null then
  :bl1.item_no := :global.form_2.item_no; end if;
--

[Quoted] :bl1.description := upper(:bl1.description);
--

convert_date_r(:bl1.ins_upd_del_date_scr,

               'bl1.ins_upd_del_date')

Now the worse part comes:

If I do step one and step two again a stack dump (!!!!!) follows.

I could "solve" this problem in the following two ways:

by creating a key exit trigger in form 1: which contains the following:

erase('global.form1_customer_order_no');
erase('global.form1_cusno');
erase('global.form1_co_line_no');
erase('global.form1_item_no');
erase('global.form1_shipment_no');

Or changing the pre query trigger in form 2:

default_value ('','GLOBAL.ITEM_NO');
if :global.item_no is not null then
  :bl1.item_no := :global.item_no;
end if;
--

if is not null then
:bl1.description := upper(:bl1.description); end if;
--

convert_date_r(:bl1.ins_upd_del_date_scr,

               'bl1.ins_upd_del_date')

both changes solve the problem. My question is why ???

If anybody does have a clue, this would be great.

Robert Received on Wed Nov 29 2000 - 22:43:43 CET