Recent content by d.morose

Uh, not exactly. With UseOCI7 = True fails both on 8.0.4 and 8.0.5 Summing it up: UseOCI7=False & 8.0.4 - fails, as expected UseOCI7=True & 8.0.4/5 - succeeds with some errors and fails with others UseOCI7=False & 8.0.5 - succeeds with all errors some mystery...

further research results (hope it'll be helpful for someone else): with above option set not any error can be located. For example, select * from dept where deptno='char' raise ORA-01722: invalid number and ErrorLine=ErrorPosition=0, while with Net8 ver>=8.0.5 will point to 'char' position...

... and it can, with TOracleSession.Preferences.UseOCI7:=true :-)

pps: but one thing remains in fog for me... SQL*Plus can do it with 8.0.4, so I guess DOA could do it too, not only with 8.0.5 and higher

oci.dll version 8.0.4.0.1 ora804.dll version 8.0.4.0.3 Tried both ps: Then I opened help ... I know I should did it before asking here. Sorry for taking your time, Marco Big thanks anyway [This message has been edited by d.morose (edited 05 November 2002).]

Well, it's INSERT or UPDATE, not SELECT. And SQL*Plus can locate error position, so why can't we? Some tricky OCI call?

Marco, it works only with parse errors. What to do with correct queries which produce errors like "ORA-01438 value larger than specified precision allows for this column"? ErrorLine and ErrorPosition will contain 1 but it's not true.

How to get detailed error information after executing TOracleQuery? EOracleError is not enough, I need exact position, like in SQL*Plus "Error at line" tnx