Forms hangs when using result of an OUT parameter to do an Insert

Question

Hello,
I think I have slightly odd problem here... I'm currently migrating a Forms 6i client-server application to Forms 10g904. I found that one of my Forms was hanging i.e. screen goes blank, 'activity' bar on the bottom right just keeps whirring away indefinitely.
After much investigation, the hanging-form problem occurs in the following scenario:
- In a routine in a Forms pll library, a variable is declared e.g. w_capture_output
- In the first round of a loop, this variable is passed into a database stored proc, which has an OUT parameter to return a result e.g. SOME_PROC(w_some_input, w_capture_output);
- w_capture_output comes back with a value e.g. 'P'
- This is then used in an Insert e.g. INSERT INTO some_table (a, b) VALUES (1, w_capture_output)
- The next round of the loop; the variable is passed in again into the proc. It still holds the value from the last round e.g. 'P'
- In this round, the logic of the proc is such that the OUT argument is set to null i.e. when the proc has finished, w_capture_output is now null. This can be confirmed with IF w_capture_output IS NULL THEN display_some_message. The code is still all running fine.
- But now when I run INSERT INTO some_table (a, b) VALUES (2, w_capture_output) - the form hangs.
I can, however, work around this and prevent the form from hanging simply by ensuring at the start of each round of the loop that I explicitly set w_capture_output back to null before passing it into the proc that sets it. Or alternatively, after it comes back from the proc, the following also prevents the hanging problem:
w_capture_output := NVL(w_capture_output,NULL);
To summarise - if I pass a variable into a proc taking an OUT parameter, AND that variable is not null going into the proc, AND the proc sets it to null AND I then try to use that variable in an Insert statement - the form hangs. Something horrible is happening to the variable inside the procedure, I think.
Now, I can kind of see why passing a non-null variable into an OUT argument might cause problems (although only if you then try to set it to null - not if you set it to another, non-null value). However, exactly the same code works fine under Forms 6i, using the same database instance and proc. And if Oracle have changed the rules, shouldn't it throw an error, rather than just hanging? I'd prefer not to have to use the workaround, as this is a very large app and I don't know yet how many places would need it.
Has anyone else come across this issue..? (Database is 9.0.2. btw, Forms are 10g904)
Cheers,
James

Answer 1

Try
v_log_name := 'Fnd_File.LOG_OUT';Hey, what r u doing with above code?
You are assigning string value to a variable?
The compilation won't give any error.
And OP thinks it's solution!!!!!!!!!!!
LOL