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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

MESSAGE built-in<br />

Description<br />

Displays specified text on the message line.<br />

Syntax<br />

PROCEDURE MESSAGE<br />

(message_string VARCHAR2,<br />

user_response NUMBER);<br />

Built-in Type unrestricted procedure<br />

Enter Query Mode yes<br />

Parameters<br />

message_string Specify a character string enclosed in single quotes or a variable of<br />

VARCHAR2 data type.<br />

user_response Specifies one of the following constants:<br />

MESSAGE restrictions<br />

ACKNOWLEDGE Specifies that <strong>Form</strong> <strong>Builder</strong> is to display a modal alert<br />

that the operator must dismiss explicitly, whenever two consecutive<br />

messages are issued. ACKNOWLEDGE forces the first message to be<br />

acknowledged before the second message can be displayed. This is the<br />

default.<br />

NO_ACKNOWLEDGE Specifies that, when two consecutive messages<br />

are issued, the operator is not expected to respond to the first message<br />

displayed before <strong>Form</strong> <strong>Builder</strong> displays a second message. Using<br />

NO_ACKNOWLEDGE creates a risk that the operator may not see the first<br />

message, because the second message immediately overwrites it without<br />

prompting the operator for acknowledgement.<br />

The message_string can be up to 200 characters long. Note, however, that several factors affect the<br />

maximum number of characters that can be displayed, including the current font and the limitations of<br />

the runtime window manager.<br />

MESSAGE examples<br />

/*<br />

** Built-in: MESSAGE<br />

** Example: Display several messages to the command line<br />

** throughout the progress of a particular<br />

** subprogram. By using the NO_ACKNOWLEDGE parameter,<br />

** we can avoid the operator’s having to<br />

** acknowledge each message explicitly.<br />

*/<br />

PROCEDURE Do_Large_Series_Of_Updates IS<br />

BEGIN<br />

Message(’Working... (0%)’, NO_ACKNOWLEDGE);<br />

283

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

Saved successfully!

Ooh no, something went wrong!