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.

Transactional Triggers property<br />

Description<br />

Identifies a block as a transactional control block; that is, a non-database block that <strong>Form</strong> <strong>Builder</strong> should<br />

manage as a transactional block. This property is included for applications that will run against non-<br />

ORACLE data sources, and that will include transactional triggers. If your application will run against<br />

ORACLE, leave this property set to No.<br />

When you create a non-ORACLE data source application, you are essentially simulating the functionality<br />

of a data block by creating a transactional control block. Such a block is a control block because its base<br />

table is not specified at design time (the Base Table block property is NULL), but it is transactional<br />

because there are transactional triggers present that cause it to function as if it were a data block.<br />

For more information, see <strong>Form</strong> <strong>Builder</strong> Advanced Techniques, Chapter 4, "Connecting to Non-<br />

ORACLE Data Sources."<br />

Applies to block<br />

Set <strong>Form</strong> <strong>Builder</strong><br />

Default<br />

No<br />

Usage Notes<br />

• Transactional Triggers applies only when the Base Table property is NULL.<br />

• Setting Transactional Triggers to Yes enables the Enforce Primary Key and Enforce Column<br />

Security properties.<br />

301

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

Saved successfully!

Ooh no, something went wrong!