This content has been marked as final. Show 6 replies
Any chance you could edit your profile to make your handle a little more personal?
And for some things, it would be nice to know what versions of Oracle and APEX you are running.
Say. Can you could set up a trivial example with one page item that shows the problem you are having. You can do this in a workspace on apex.oracle.com? Or better yet. Look at my example.
Logon here with Dever / Ima9Dever http://apex.oracle.com/pls/apex/f?p=43250:3
On page 3, look at the item P3_X_ASTERISK with a default value of *.
There's not enough detail in your post to be certain what is happening. However, quite often when something like this happens, what you'll find is that you are trying to access a page item before it gets set. The sequence being something like this:
Enter Page 10
Try to access P10_SOMEVALUE. Value is NULL.
P10_SOMEVALUE is set to its default value of 15.
Re-enter Page 10
Try to access P10_SOMEVALUE. Value is 15
I can't say for certain this is what you are encountering, but it's something that I've seen on many occasions.
I second what Matthew has said. There is every expectation that APEX is going to do things in 1, 2, 3, ... order. You enter the page, the value is NULL. It gets initialized. Sure. But then it doesn't work!
I've spent a whole day working with one thing after another ... it seems to work ... but I add another piece and then it doesn't work again. It's hard to debug unless you clear the Session State and start over cleanly each time you begin to test something.
Then it all falls into place but you aren't sure what you were doing wrong the whole time. Maddening!
Best of luck,
Hi Matthew and Howard
Thanks so much for your replies.. Yes I am encountering the exact situation as what Matthew described... so is there any solution for it? Is there any way the page item can be set the moment the page is loaded for the first time?
And I am using Apex 4.1 and Oracle 11g.
Thanks in advance.
Edited by: 971331 on Nov 14, 2012 9:46 PM