Data type conversion error.
Posted: Wed 10 Sep 2008 13:47
Hi support.
I have been getting troubles with the ODAC 6.50.xx version. It allows the TOraQuery componnent to deal with parameters of data types not suported by C++Builder like "Number" and "varchar". This behaviour is responsible for the raising of conversion errors at runtime. Bellow ther is an example of code that is raising this exception.
A TOraQuery with the SQL comand bellow:
The parameters were defined at design time with the proper ones (ftInteger and ftString ).
The code bellow sets the macro value :
When the "Prepare" method is called the parameters data types are changed to "Varchar" instead of "String" and the "Conversion" error is raised on the "Open" method call.
Is there any solution ? The OraTool Add-in also do not support the 11g Client while ODAC components do !
Thank you very much.
Jayme Jeffman
I have been getting troubles with the ODAC 6.50.xx version. It allows the TOraQuery componnent to deal with parameters of data types not suported by C++Builder like "Number" and "varchar". This behaviour is responsible for the raising of conversion errors at runtime. Bellow ther is an example of code that is raising this exception.
A TOraQuery with the SQL comand bellow:
Code: Select all
SELECT
pri.name,
DECODE(DECODE(SUBSTR(dv.current_status,1,1), null, SUBSTR(cn.normal_status,1,1), SUBSTR(dv.current_status,1,1)),'C','1','O','0','0') estado -- estado do logico
FROM
&dbowner.oms_connectivity@&dblink cn,
&dbowner.device_status@&dblink dv,
&dbowner.&tb_primary@&dblink pri
WHERE
pri.feeder_id = :alimentador AND
pri.name = :nome_eqp AND
cn.mslink = pri.mslink AND
dv.mslink (+) = cn.mslink
The code bellow sets the macro value :
Code: Select all
getLoad_Status->UnPrepare();
getLoad_Status->MacroByName("tb_primary")->Value = "OMS_BREAKER";
getLoad_Status->Prepare();
getLoad_Status->ParamByName("alimentador")->AsString = al->GetId();
getLoad_Status->ParamByName("nome_eqp")->AsString = nome_eqp2;
getLoad_Status->Open();
Is there any solution ? The OraTool Add-in also do not support the 11g Client while ODAC components do !
Thank you very much.
Jayme Jeffman