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.

Current Status Target<br />

Status<br />

408<br />

NEW QUERY INSERT CHANGED<br />

NEW yes yes1 yes2 no<br />

QUERY yes4 yes no yes<br />

INSERT yes4 yes3 yes no<br />

CHANGED yes4 no no yes<br />

1. Adheres to the rules described in footnotes 2 and 3.<br />

2. This transition is not allowed in query mode, because QUERY and INSERT are not valid in query<br />

mode.<br />

3. If this transition is performed while Runform is running in Unique Key mode and not all of the<br />

transactional triggers exist, then you must enter a valid value in the ROWID field. Put another way, if<br />

you are connected to a non-ORACLE data source that does not support ROWID, but you are using a<br />

unique key, you must supply the key for a record that goes from Insert to Query, in one of the<br />

transactional triggers, either On-Lock, On-Update, or On-Delete. Otherwise <strong>Form</strong> <strong>Builder</strong> returns an<br />

error.<br />

4. Records that have been changed but not yet committed or cleared cannot be assigned a status of NEW.<br />

SET_RECORD_PROPERTY examples<br />

/*<br />

** Built-in: SET_RECORD_PROPERTY<br />

** Example: Mark the third record in the EMP block as if it<br />

** were a queried record.<br />

*/<br />

BEGIN<br />

Set_Record_Property( 3, ’EMP’, STATUS, QUERY_STATUS);<br />

END;

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

Saved successfully!

Ooh no, something went wrong!