frm-41214: unable to run report [message #271755] |
Tue, 02 October 2007 15:52 |
scorpiouno
Messages: 6 Registered: October 2007 Location: Sparta
|
Junior Member |
|
|
i know that there are other threads that discuss this topic in quite some detail but i feel that the problem i am having is quite different from those. please read on and see if you can provide a solution.
when i test the form on the client(windows OS), which calls on reports according to parameters provided (there is a local reports server running) the form works fine and everything is as it should be.
however, when i move the fmb files to unix and run them from the fmx files generated after compilation, i can enter all the parameters and when i press the button that calls on the procedure to run the report specified in the parameters, it gives this error. i have tried looking at the code to see if there is any data type mismatch but could not find any such problem as suggested for ora-06502. i am provding part of the code used in our forms only as the rest is confidential. please provide any assistance you can asap.
before the frm 40735 comes up, there is a popup window that gives me the error frm-41214: unable to run report. is this the actual reason for the error?
when the 'compile' button is pressed, this is the procedure called using 'when-button-pressed' trigger.
runreport(:rep_setup.rep_id, :rep_setup.group_id, :rep_setup.rep_filename);
the first 2 parameters are declared as NUMBER and the third one as VARCHAR2
the data types for those three parameters from the property palette in forms builder are number, number and char in the respective order.
if it helps, the popup message that i get immediately on pressing the button is "frm-41214:unable to run report".
why is this error only when run in unix?
if you have more questions for me to help solve this, plz let me know.
[Updated on: Wed, 03 October 2007 13:32] Report message to a moderator
|
|
|
|
Re: frm-40735: when-button-pressed trigger raised unhandled exception ora-06502 [message #271952 is a reply to message #271821] |
Wed, 03 October 2007 08:06 |
scorpiouno
Messages: 6 Registered: October 2007 Location: Sparta
|
Junior Member |
|
|
the number size hasnt been mentioned in the declaration of the number variable. so the size of that should not be an issue. i will check and see if the database being connected to is the same when run in windows and unix and get back on that. in the meanwhile, can you please explain how that will affect the performance of the report in case the databases being connected to are different?
|
|
|
|
|
|
|