Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
How do I capture FRM-40505 when executing query?
2,460 views
Skip to first unread message
M Hamilton
Mar 16, 2004, 10:20:43 AM3/16/04
to
Am working in Designer 6i Forms. After entering a Query, then pressing
F8 to execute, I get the FRM-40505: ORACLE error: Unable to perform
query. I have tried coding the Application Logic Events for ON-ERROR
and ON-MESSAGE at the form level and module component level to capture
this. But, have had no luck. Can you help me capture this
error/message/alert so that the user will not see it? Thanks, Maggie
F8 to execute, I get the FRM-40505: ORACLE error: Unable to perform
query. I have tried coding the Application Logic Events for ON-ERROR
and ON-MESSAGE at the form level and module component level to capture
this. But, have had no luck. Can you help me capture this
error/message/alert so that the user will not see it? Thanks, Maggie
Luc Gyselinck
Mar 16, 2004, 4:18:57 PM3/16/04
to
Why should you hide the error?
Either the user has done something wrong, or the developer did something
wrong.
FRM-40505: ORACLE error: means that the SQL generated by forms is not
correct: columns that are marked as database are not table/view columns, the
order by, the where clause is not correct, etc. etc. Use the 'Show Error' in
the menu to view the SQL behind the query. We, developers, use this
'feature' to view the SQL of the query: force an error, view the error and
you see the SQL...
Either the user has done something wrong, or the developer did something
wrong.
FRM-40505: ORACLE error: means that the SQL generated by forms is not
correct: columns that are marked as database are not table/view columns, the
order by, the where clause is not correct, etc. etc. Use the 'Show Error' in
the menu to view the SQL behind the query. We, developers, use this
'feature' to view the SQL of the query: force an error, view the error and
you see the SQL...
"M Hamilton" <mham...@usgs.gov> wrote in message
news:7ce65461.04031...@posting.google.com...
M Hamilton
Mar 18, 2004, 9:37:42 AM3/18/04
to
It turned out, after checking out the SQL the system was generating,
that the validation was going on at 3 different places. Two were
deleted and now it is running great. No more FRM-40505 error.
that the validation was going on at 3 different places. Two were
deleted and now it is running great. No more FRM-40505 error.
"Luc Gyselinck" <Luc.Gy...@nospampandora.be> wrote in message news:<5bK5c.37630$084.2...@phobos.telenet-ops.be>...
0 new messages