Home » Developer & Programmer » Forms » Form_trigger_failure restrictions
Form_trigger_failure restrictions [message #187941] Wed, 16 August 2006 07:11 Go to next message
Messages: 33
Registered: February 2006
Location: Saudi Arabia

Hi to all,

I am raising the Form_trigger_failure in the ON-COMMIT trigger.
That is after when I check for the required items. But the problem it is showing non-oracle exception!!!
if :iso_process.process_no is null or :iso_process.process_no = '' 
or  :iso_process.process_name is null or :iso_process.process_name = ''
or :iso_process.DOC_LINK is null or :iso_process.DOC_LINK = ''then
  al_id := Find_Alert('Alert1');
  Set_Alert_Property(al_id, alert_message_text, 'You have to   
  fill all yellow fields');
  al_button := Show_Alert( 'Alert1');
  Raise form_trigger_failure;

 when others then

Is there any restriction for using RASIE Form_trigger_Failure in the ON-COMMIT Trigger?

[Updated on: Wed, 06 September 2006 21:31] by Moderator

Report message to a moderator

Re: Form_trigger_failure restrictions [message #191519 is a reply to message #187941] Wed, 06 September 2006 21:36 Go to previous message
Messages: 10180
Registered: March 2005
Location: Surges Bay TAS Australia
Senior Member
Account Moderator
Have you fixed your problem?

What is the non-Oracle exception that is being raised?

I feel that the 'on-commit' trigger is too late in the processing sequence, use the 'pre-commit' trigger instead.

Reference Manual says

Usage Notes
- Use an On-Commit trigger to change the conditions of normal Form Builder commit processing to fit the particular requirements of a commit to a non-ORACLE database.


[Updated on: Wed, 06 September 2006 21:42]

Report message to a moderator

Previous Topic: FRM 40508
Next Topic: insert into every record value from lov in Oracle forms
Goto Forum:

Current Time: Wed Aug 23 10:33:17 CDT 2017

Total time taken to generate the page: 0.07707 seconds