| apex [message #585420] |
Sat, 25 May 2013 03:25  |
 |
ariffcal
Messages: 107
Registered: April 2011
|
Senior Member |
|
|
I have created a form and interactive report with a table , cargo .
However , when I enter data in forms and click save , the data is not inserted in the table , cargo.
Pls help , and let me know the solution
|
|
|
|
|
|
|
|
|
|
|
|
| Re: error ora-44003 [message #585511 is a reply to message #585508] |
Mon, 27 May 2013 03:03  |
John Watson
Messages: 8964
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
The "ORA-44003: invalid SQL name" return code can actually be a useful return code. I've seen it used, with dbms_assert, to detect attempts to hack web applications by sending URLs that include strings that might be appended to dynamic SQL statement. Like this, where I test whether a value is a legitimate object name (though not whether it exists) or not:orcl>
orcl> select dbms_assert.simple_sql_name('emp') from dual;
DBMS_ASSERT.SIMPLE_SQL_NAME('EMP')
---------------------------------------------------------------------------------
emp
orcl> select dbms_assert.simple_sql_name('emp and nasty_function=0') from dual;
select dbms_assert.simple_sql_name('emp and nasty_function=0') from dual
*
ERROR at line 1:
ORA-44003: invalid SQL name
ORA-06512: at "SYS.DBMS_ASSERT", line 160
orcl>
I think the idea is that programmers should always test every parameter to make sure it is what they expect. Almost certainly, there is something in OP's form that refers to an impossible table name: one with spaces or some such.
|
|
|
|
|
|
|
|
| Re: error ora-44003 [message #585518 is a reply to message #585517] |
Mon, 27 May 2013 03:54 |
 |
Littlefoot
Messages: 21823
Registered: June 2005
Location: Croatia, Europe
|
Senior Member
Account Moderator |
|
|
Quote:I made the fedid column to hidden
As far as I can tell, that does NOT affect form's execution (not in a way you described).
Quote:the again changed it to primary key
Where and how did you do that? Why did you do that? It already was a primary key column, wasn't it? HIDDEN attribute doesn't change that.
Did you, by any chance, delete that item, and then tried to recreate it manually?
[Updated on: Mon, 27 May 2013 03:54] Report message to a moderator |
|
|
|
|
|
| Re: error ora-44003 [message #585522 is a reply to message #585520] |
Mon, 27 May 2013 04:17 |
|
Littlefoot
Messages: 21823
Registered: June 2005
Location: Croatia, Europe
|
Senior Member
Account Moderator |
|
|
In supporting objects? Which Apex version do you use?
On Apex 4.1, I tried to simulate why you said:- created a table:
create table a1_test
(id number constraint pk_test primary key,
ime varchar2(20)); - created a form with report, using Wizard
- ran the form, inserted a record
- dropped the constraint
alter table a1_test drop constraint pk_test; - ran the form again, inserted another record
- set the ID item "hidden"
- ran the form again, inserted yet another record (whose ID column is now, obviously, empty)
- recreated the primary key constraint:
alter table a1_test add constraint
pk_test primary key (id)
enable novalidate; - set the ID column to be a "text" item again
- ran the form, inserted 4th record
Everything worked just fine, no problems at all.
If you could explain, step by step, what you did, maybe it would be easier to assist. Or, create an application on apex.oracle.com (you can get a free workspace there; let us know credentials so that we could access it). The way it is now, I still have no idea what went wrong.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
