Extremely Weird Error After Upgrading to 10G [message #500812] |
Wed, 23 March 2011 12:29 |
Curious_Programmer
Messages: 11 Registered: October 2009
|
Junior Member |
|
|
So I have an extremely weird error that I just found after several month of being upgraded to 10g from 6i. Right now I have several data blocks where users input data. The field that they input into is fairly long, so we give them the option to double-click which opens up the editor.
Now, if they do this when entering the field for the first time, everything works great. However, if they save, then decide to go back into the data block and edit the field, they can edit it in the text just fine. However, if they double-click and bring up the text editor, after they click ok (or cancel) it jumps back to the first data block.
What is more weird is I can't get it to happen on my own machine, only when it is running on the unix server. On top of that, I was able to avoid the issue by simply showing a message saying "field is about to be edited" and making them click ok. Of course, it's a work-around, but an annoying one, so if anyone has any ideas of what may be causing this, please feel free to offer any suggestions.
Thank you in advance,
|
|
|
|
|
|
Re: Extremely Weird Error After Upgrading to 10G [message #501705 is a reply to message #501205] |
Wed, 30 March 2011 16:08 |
Curious_Programmer
Messages: 11 Registered: October 2009
|
Junior Member |
|
|
SO just to update where I am on this. I erased the editor we were using before, and it now jumps to a different data block (even though it still jumps for no reason).
Since I know that showing a message or an alert (or even a bug message works), is there a way to do this but not show it to the user....?
|
|
|
Re: Extremely Weird Error After Upgrading to 10G [message #501740 is a reply to message #501705] |
Thu, 31 March 2011 00:45 |
|
Littlefoot
Messages: 21823 Registered: June 2005 Location: Croatia, Europe
|
Senior Member Account Moderator |
|
|
To issue an "invisible" message? You could try it by adjusting the :SYSTEM.MESSAGE_LEVEL value, such as
decode
l_level number;
begin
-- save previous level value
l_level := :system.message_level;
:system.message_level := 25;
message('Your message');
-- restore
:system.message_level := l_level;
end;
[Updated on: Thu, 31 March 2011 00:45] Report message to a moderator
|
|
|