1Z0-151 · Question #17
You want to use the Forms Debugger to diagnose a problem with the RAISE_STATUS program unit that is stored in the database. Forms Builder, you set a breakpoint in the stored code, and then run the…
The correct answer is D. You cannot use the Forms Debugger to diagnose problems with stored program units. The Forms debugger can only step through Forms side code, not database side code. If you Form calls a database procedure, you will not be able to see what it does through the Forms
Question
You want to use the Forms Debugger to diagnose a problem with the RAISE_STATUS program unit that is stored in the database. Forms Builder, you set a breakpoint in the stored code, and then run the Human Resources form in debug mode. You click the Raise_Salaries button, which has a When Button Pressed trigger that calls RAISE_SALARIES. However, you are unable to see the RAISE_SALARIES procedure when you step through the code, and it does not appear in the stack frame. What could be the reason for this problem?
Options
- AYou are not connected to the database.
- BThe stored program unit was not compiled with the debug information included.
- CThe breakpoint should have been set in the When-Button-Pressed trigger, not in the stored program unit.
- DYou cannot use the Forms Debugger to diagnose problems with stored program units.
How the community answered
(58 responses)- A16% (9)
- B3% (2)
- C9% (5)
- D72% (42)
Explanation
The Forms debugger can only step through Forms side code, not database side code. If you Form calls a database procedure, you will not be able to see what it does through the Forms
Topics
Community Discussion
No community discussion yet for this question.