11.01.2013 Views

Oracle Forms Developer – Form Builder Reference, Volume 1

Oracle Forms Developer – Form Builder Reference, Volume 1

Oracle Forms Developer – Form Builder Reference, Volume 1

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

348<br />

SYNCHRONOUS specifies that control returns to <strong>Form</strong> <strong>Builder</strong> only after<br />

the called product has been exited. The end user cannot work in the form<br />

while the called product is running.<br />

ASYNCHRONOUS specifies that control returns to the calling application<br />

immediately, even if the called application has not completed its display.<br />

execmode Specifies the execution mode to be used when running the called product.<br />

Valid numeric constants for this parameter are BATCH and RUNTIME.<br />

When you run Report <strong>Builder</strong> and Graphics <strong>Builder</strong>, execmode can be<br />

either BATCH or RUNTIME. When you run <strong>Form</strong> <strong>Builder</strong>, always set<br />

execmode to RUNTIME.<br />

locatioSpecifies the location of the module or module you want the called product to execute, either the<br />

file system or the database. Valid constants for this property are<br />

FILESYSTEM and DB.<br />

Paramlist_name or paramlist_ID Specifies the parameter list to be passed to the called product. Valid<br />

values for this parameter are the VARCHAR2 name of the parameter list,<br />

the ID of the parameter list, or a null string (’’). To specify a parameter list<br />

ID, use a variable of type PARAMLIST.<br />

You can pass text parameters to called products in both SYNCHRONOUS<br />

and ASYNCHRONOUS mode. However, parameter lists that contain<br />

parameters of type DATA_PARAMETER (pointers to record groups) can<br />

only be passed to Report <strong>Builder</strong> and Graphics <strong>Builder</strong> in<br />

SYNCHRONOUS mode. (SYNCHRONOUS mode is required when<br />

invoking Graphics <strong>Builder</strong> to return an Graphics <strong>Builder</strong> display that will<br />

be displayed in a form chart item.)<br />

Note: You can prevent Graphics <strong>Builder</strong> from logging on by passing a<br />

parameter list that includes a parameter with key set to LOGON and value<br />

set to NO.<br />

Note: You cannot pass a DATA_PARAMETER to a child query in Report<br />

<strong>Builder</strong>. Data passing is supported only for master queries.<br />

display Specifies the VARCHAR2 name of the <strong>Form</strong> <strong>Builder</strong> chart item that will<br />

contain the display (such as a pie chart, bar chart, or graph) generated by<br />

Graphics <strong>Builder</strong>. The name of the chart item must be specified in the<br />

format block_name.item_name. (This parameter is only required when you<br />

are using an Graphics <strong>Builder</strong> chart item in a form.)<br />

RUN_PRODUCT examples<br />

/*<br />

** Built-in: RUN_PRODUCT<br />

** Example: Call a Report <strong>Builder</strong> report, passing the<br />

** data in record group ’EMP_RECS’ to substitute<br />

** for the report’s query named ’EMP_QUERY’.<br />

** Presumes the Emp_Recs record group already<br />

** exists and has the same column/data type<br />

** structure as the report’s Emp_Query query.<br />

*/<br />

PROCEDURE Run_Emp_Report IS<br />

pl_id ParamList;<br />

BEGIN<br />

/*<br />

** Check to see if the ’tmpdata’ parameter list exists.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!