Transaction Boundaries for Power Browse Forms and Subforms

Power forms include the Transaction property, which functions the same as the other form types. By default, it is scoped to OK button processing; however, the scope can be extended to business functions, table I/O, and form interconnects.

Subforms are scoped to Save button processing; however, the scope can be extended to business functions, table I/O, and form interconnects. You can use these transaction processing settings for subforms:

Setting	Result
Transaction Disabled (default)	No transaction processing occurs for this form.
Include in Parent Transaction	If the form is called within the parent's transaction boundary (OK or Save processing), the transaction will be included in the parent's transaction boundary.
Subform Only Transaction	Save processing for the Subform has its own transaction boundary, which is independent of all boundaries.

This flowchart illustrates how to include all of the subforms in the form save transaction. If you rollback data on any one form, the system rolls back the changes on all of them:

Including parent, child, and grandchild in the transaction boundary.

Here, the child is not included in the transaction for the form, which means that a rollback on the parent level will not affect any of the subforms. However, all of the subforms are included in the same transaction, so any rollback on the subforms will affect all of the subforms:

Placing parent in a separate transaction boundary from its child and grandchild.

In all these scenarios, transactions are local and will not affect appear on any other form:

Placing parent, child, and grandchild in separate transaction boundaries.