OraFAQ Forum: Forms » How to capture the Oracleforms error

Home » Developer & Programmer » Forms » How to capture the Oracleforms error

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

How to capture the Oracleforms error [message #292594]

Wed, 09 January 2008 05:38

ap_karthi
Messages: 87
Registered: October 2007
Location: Bangalore

Member

Hi,

I got an error, "ORACLE error: unable to DELETE record. - (40510)", when tried to delete a record in the form. Actually we dont know why this error is showing.

We have to press SHIFT + F1, then we will know whats the error is like...
ORA-02292: integrity constraint (FK_BT) violated - child record found
ORA-06512: at "SSSS", line 70
ORA-04088: error during execution of trigger 'FCCC'

Without pressing SHIFT+F1, is there any other way to view or capture the error.

Thank you...

-Karthik

Report message to a moderator

Re: How to capture the Oracleforms error [message #292683 is a reply to message #292594]

Wed, 09 January 2008 10:59

varu123
Messages: 754
Registered: October 2007

Senior Member

well,I can't say for sure but something like

BEGIN
  IF Error_Type = 'FRM'
     AND Error_Code = 40510 THEN
    Message('ORA-02292: integrity constraint (FK_BT) violated - child record found
');
  END IF;
END;

Report message to a moderator

Re: How to capture the Oracleforms error [message #292699 is a reply to message #292594]

Wed, 09 January 2008 12:15

Littlefoot
Messages: 21823
Registered: June 2005
Location: Croatia, Europe

Senior Member
Account Moderator

Just being curious ... what's wrong with <Shift + F1>?

Report message to a moderator

Re: How to capture the Oracleforms error [message #292835 is a reply to message #292683]

Thu, 10 January 2008 00:29

ap_karthi
Messages: 87
Registered: October 2007
Location: Bangalore

Member

There is a chance not only child record, some other errors also possible. So we dont know what error is throwing in the client side, because will say to us that we are not able to delete, so without connecting to the user machine we have to get the error using mail or stored in database.

Report message to a moderator

Re: How to capture the Oracleforms error [message #292837 is a reply to message #292699]

Thu, 10 January 2008 00:33

ap_karthi
Messages: 87
Registered: October 2007
Location: Bangalore

Member

We developer know the funtion of <Shift +f1>, but user doesnt know. For him it will show "cannot delete" or "cannot update" or some other errors only.

Incase, if we are not able to connect to the user system and before he explains us, we can write a program, so that the errors can be stored in the table or mail to us, whatever error is showing while viewing using shift+f1.

Report message to a moderator

Re: How to capture the Oracleforms error [message #292896 is a reply to message #292837]

Thu, 10 January 2008 02:30

Littlefoot
Messages: 21823
Registered: June 2005
Location: Croatia, Europe

Senior Member
Account Moderator

When you will write user documentation, make sure to mention that details about errors can be viewed by pressing <Shift + F1> keys.

When your users first saw the application, I believe they didn't know how to use it. How did you explain them that, for example, they will enter query mode by pressing F7 and execute a query by pressing F8? Were they born with a knowledge that a key which says "Backspace" actually deletes letters? Etc. etc.

Besides, once there were video terminals; when PC's came to their desks, they had to learn how to use a mouse, and that was a far more complicated action than pressing <Shift + F1>, believe me.

A conclusion: there's nothing wrong in telling people that <Shift + F1> reveals extra information about errors.

Report message to a moderator