Re: Forms 5.0 ( Run_Product) Misbehaving.

From: Andy Hardy <aph_at_ahardy.demon.co.uk>
Date: Sun, 13 Jun 1999 02:06:47 +0100
Message-ID: <cRvF2sAnQwY3EwnT_at_ahardy.demon.co.uk>


In article <7j101t$8f4$1_at_nnrp1.deja.com>, rtproffitt_at_my-deja.com writes
>Margot is correct.
>
>Here is a paste from Oracle online help:
>Syntax
>
>PROCEDURE RUN_PRODUCT
> (product NUMBER,
> module VARCHAR2,
> commmode NUMBER,
> execmode NUMBER,
> location NUMBER,
> paramlist_id VARCHAR2,
> display VARCHAR2);
>PROCEDURE RUN_PRODUCT
> (product NUMBER,
> module VARCHAR2,
> commmode NUMBER,
> execmode NUMBER,
> location NUMBER,
> paramlist_name VARCHAR2,
> display VARCHAR2);
>
>When you call
> Run_Product(REPORTS,:control_blk.rpt_choice,SYNCHRONOUS,
> RUNTIME,FILESYSTEM,NULL,NULL);
>with two NULLS, there is no way for the parser to figure out
>which of the two syntactical forms you are calling.

Which would point to an Oracle documentation error (at least in F45):

list or name Specifies the parameter list to be passed to the called product. Valid values for this parameter are the CHAR name of the parameter list, the ID of the parameter list, or NULL. To specify a parameter list ID, use a variable of type PARAMLIST.

Copyright (c) 1994, Oracle Corporation.

However, one of the examples is

Run_Product(REPORTS,'stats',ASYNCHRONOUS,BATCH,FILESYSTEM);

Copyright (c) 1994, Oracle Corporation.

which would seem to show that the two NULLs are not necessary.

Looking at the F45 declaration, it shows the paramlist_id being of type PARAMLIST and name of type CHAR. Setting this value to NULL would mean that it could not tell which form of run_product was required.

Andy
>But when you declare a variable and assign it null,
>as with Margot's suggestion, then the parser knows
>exactly which syntax you are using, and is no longer
>confused.
>
>Robert Proffitt
>Beckman Coulter
>Brea California
>RTProffitt_at_beckman.com
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.

-- 
Andy Hardy. PGP key available on request
===============================================================
Received on Sun Jun 13 1999 - 03:06:47 CEST

Original text of this message