It is possible that the code is not filling in the key properly. Maybe is is blank and that is whay I am getting the 'No Record Found' error; but I have not found a way to confirm this. I tried 'debug' but it didn't seem to show the values of the items.
What is the purpose of the single pipe character that follows the "F" in the line of code APEX does not like?
It looks like APEX is trying to concatenate the character F on the froont of the schema name. I am assuming #OWNER# is the schema name. But why it is doing this, I don't know. This seems to be the only place on page 2 where APEX is generating this "F|#OWNERNAME# string.
I removed the F|, imported the page and gave it another try. I got the same error
Hmmm... are you using the l_clob and l_length variables anywhere?
And I'm not sure, at least from what I see, that line 1 column 9 is necessarily referring to the | character. But neither do I know where else it could be. Is this something you could replicate on apex.oracle.com?
This is a Microsoft Access application that I migrated to APEX. All of the reports came over flawlessly - all I had to do was make minor visual changes to report titles. All of the functional forms (non-reports) gives the following error:
ORA-01403: no data found
Error Unable to fetch row. OK
When I debug they all fail at "...Process "Fetch Row from.... " and each failure has this F|#OWNER" specification in it.
Maybe the F|#OWNER# is a carry over artifact of Microsoft Access...
You might be on to something regarding Microsoft Access artifacts. Perhaps swapping out the msaccess_utilities.datediff function with an Oracle function would make a difference. I'm surprised that even works, because I am unable to SELECT that function from DUAL. What version of APEX on what version of database are you using?
Is perfectly valid, it is an APEX DML string
F = Fetch
#OWNER# = the schema from the workspace
QS_SPECIFICHHNO = the table/view
P2_HHNO = The APEX item to match with the key
HHNO = The key in the table/view
The p_runtime_where_clause appears to be invalid;
a) The "WHERE" keyword is not necessary, also it should be '&P2_HHNO.' not '&P2_HHNO'
b) The record should have already matched using the DML string
Try deleting the runtime_where_clause, it should then work.
sbing52, was the information from RecxLtd helpful?
Thanks for the explanation. I am just a newbie on Apex. So when I encounter that type of string, it is simply APEX shorthand for a SQL statement.
Every little bit of information helps to bring the entire picture into focus.
Simplified, yes, it is 'shorthand' for a SQL with a where clause.
It allows items on the page with a source of 'Database Column' to access the data from the current DML selection (Sometimes called Automatic Row Fetch).