|
|
|
|
|
|
Re: When I try to run a form I am getting the below error, FRM: 40735 When window activated trigger rais [message #627886 is a reply to message #627724] |
Mon, 17 November 2014 16:33 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) |
![](//www.gravatar.com/avatar/6f539f43889b4b3e3fcb6c591073de8f?s=64&d=mm&r=g) |
CraigB
Messages: 386 Registered: August 2014 Location: Utah, USA
|
Senior Member |
|
|
I suggest you do as cookiemonster first suggested. Put Message() calls in your code so you can pinpoint where in your code the error occurs. You can either call Message() twice - which puts a new message on the stack and promotes the first one to an Alert or you can use MESSAGE(); and PAUSE; If you use the Message/Pause your debugging message will display in the Status Bar. Here is an example of what I'm talking about...
PROCEDURE P_FORM_STARTUP IS
L_wh wh.wh%TYPE := NULL;
cursor C_RECORD_EXISTS is
select wh
from wh_attributes
where wh = :PARAMETER.PM_wh;
BEGIN
Clear_Message;
Message('Calling P_INITIALIZE');
Message(' '); -- This will promote "Calling P_INITIALIZE" to the default Alert
P_INITIALIZE;
Clear_Message;
Message('Setting System.Message_Level');
Pause; -- This will "Pause" execution by displaying a blank Alert with a OK
-- button so you can see the message in the Status Bar
:system.message_level := F_message_level;
...Rest of your code here...
The less tedious method would be to learn how to use the Forms Debugger. Then you can watch each line of code execute so you don't have to use all of the debug messages in your code and you don't have to worry about accidently leaving one in when your form gets deployed to your production environment.
Craig...
|
|
|