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.

session_mode NO_SESSION (The default.) Specifies that the opened form should<br />

share the same database session as the current form. POST and COMMIT<br />

operations in any form will cause posting, validation, and commit<br />

processing to occur for all forms running in the same session.<br />

SESSION Specifies that a new, separate database session should be<br />

created for the opened form.<br />

data_mode NO_SHARE_LIBRARY_DATA (The default.) At runtime, <strong>Form</strong><br />

<strong>Builder</strong> will not share data between forms that have identical libraries<br />

attached (at design time).<br />

SHARE_LIBRARY_DATA At runtime, <strong>Form</strong> <strong>Builder</strong> will share data<br />

between forms that have identical libraries attached (at design time).<br />

paramlist_name The name of a parameter list to be passed to the opened form. Datatype is<br />

VARCHAR2.<br />

paramlist_id The unique ID that <strong>Form</strong> <strong>Builder</strong> assigns to the parameter list at the time it<br />

is created. Use the GET_PARAMETER_LIST function to return the ID to<br />

a variable of type PARAMLIST.<br />

Usage Notes<br />

• Whether you open a form with ACTIVATE or NO_ACTIVATE specified, any startup triggers that<br />

would normally fire will execute in the opened form. (However, see the usage note regarding<br />

SESSION-specified below.)<br />

• When you open a form with ACTIVATE specified (the default), the opened form receives focus<br />

immediately; trigger statements that follow the call to OPEN_FORM never execute.<br />

• When you open a form with NO_ACTIVATE specified, trigger statements that follow the call to<br />

OPEN_FORM will execute after the opened form has been loaded into memory and its initial startup<br />

triggers have fired.<br />

• When you open a form with SESSION specified, the PRE-LOGON, ON-LOGON, and POST-<br />

LOGON triggers will not fire.<br />

• If the form that issues the OPEN_FORM built-in is running in QUERY_ONLY mode, then the<br />

opened form will also run in QUERY_ONLY mode.<br />

• On Microsoft Windows, if any window in the form that opens the independent form is maximized,<br />

the first window displayed by the opened form will also be maximized, regardless of its original<br />

design-time setting. (The GUI display state of a window is controlled by the Window_State<br />

property.)<br />

• For most applications, you should avoid using OPEN_FORM with forms that contain root windows.<br />

Because there can be only one root window displayed at a time, canvases that are assigned to the<br />

root window in the current form and in the opened form will be displayed in the same window. This<br />

causes the opened form to "take over" the root window from the original form, thus hiding the<br />

canvases in the original form partially or completely.<br />

OPEN_FORM restrictions<br />

• You can set session On for all Runform invocations by setting the FORMSnn_SESSION<br />

environment variable to TRUE. When you set the FORMSnn_SESSION variable, all Runform<br />

invocations inherit its setting, unless you override the environment variable by setting the Session<br />

option from the Runform command line.<br />

307

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

Saved successfully!

Ooh no, something went wrong!