What could be the reason for this problem?

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?

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?

A.
You are not connected to the database.

B.
The stored program unit was notcompiledwith the debuginformationincluded.

C.
The breakpoint should have been setinthe When-Button-Pressed trigger, notinthe stored
program unit.

D.
You cannot use the Forms Debugger to diagnose problems with stored program units.

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 debugger.



Leave a Reply 2

Your email address will not be published. Required fields are marked *


ngayathri81

ngayathri81

B is correct answer

RAHIM JAN

RAHIM JAN

ngayathri81 b is not correct D IS CORRECT