This preview shows page 1. Sign up to view the full content.
Unformatted text preview: ooking at the exhibit, assuming that the
master-detail triggers and relations have not been modified since they were created?
A. Users will be unable to delete detail records if master records exist.
B. Users will be unable to delete master records of detail records exist.
Actualtests.com - The Power of Knowing 1Z0-141
C. If users delete a master record, its detail records will also be deleted.
D. Users will be able to delete a master record even if detail records exist.
E. If users delete all detail records, the master record will also be deleted.
There is a requirement to change the default functionality of certain function keys (suck as [Exit], [Create
Record], [Duplicate Record], and so on) when the focus is in the INVENTORIES block of the Orders form.
If the user presses the [Exit] key, the focus should be transferred to the ORDER_ITEMS block. Pressing the
other function keys should cause a meaningful message to appear.
How can you meet this requirement?
A. Use of Key triggers at the form level only is sufficient, but the Exception Hierarchy property of the trigger
must be set to Override.
Form example, the Key-Exit trigger has the following code:
B. Use a Key triggers written on the INVENTORIES block only is sufficient.
For example, the Key-Exit trigger has the following code:
C. Use a combination of block- and form-level Key triggers.
For example, the Key-Exit trigger on the INVENTORIES block has the following code:
The form-level Key-Others trigger has the following code:
D. Use a Key-Others trigger written at the form level with the Execution Hierarchy property of the trigger set to
The code can be written generically to test for the current block and to use the DO_KEY built-in to exit the
For example, it has the following code:
IF :SYSTEM.trigger_block = 'INVENTORIES' THEN
Exhibit: Actualtests.com - The Power of Knowin...
View Full Document
This document was uploaded on 03/08/2014.
- Fall '09