| How to trap the FRM-47017 error ? [message #366255] |
Fri, 12 December 2008 05:30  |
raywong9i
Messages: 40
Registered: April 2008
|
Member |
|
|
Hi all,
I need to delete a parameter ('branch code') from a parameter list, but this parameter is not always in the list.
I come to the problem that, if the branch code is not in the list and I try to delete it, the FRM-47017 error will popup. I need to suppress this error message.
I try to use exception to trap the error as follows , but not succeed :
begin
delete_parameter(pl_id, 'BRANCH_CODE')
exception
when others then
null;
end;
Also, I try to set the SYSTEM.MESSAGE_LEVEL, still with no luck.
Now I use the ON-ERROR to handle the error, but I have 150 forms that will do the same thing, how can I avoid adding 150 ON-ERROR triggers but still can suppress the error ?
Thanks!
|
|
|
|
| Re: How to trap the FRM-47017 error ? [message #375822 is a reply to message #366255] |
Mon, 15 December 2008 00:58  |
 |
djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia
|
Senior Member
Account Moderator |
|
|
I think I fixed this at a previous site some 8 years ago by building a completely new parameter list that did not include the ones that I had initially tried to delete.
Perhaps using nested 'begin exception; end;' statements might get around the problem. Sorry, I can't remember the final solution we used.
David
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
