DUMPu00B4s with SQL

Former Member — Thu, 09 Oct 2008 21:31:36 GMT

I 'm using SQL sentences in a customer program, for example:


        EXEC SQL.
          INSERT INTO ORAGNI.V_SALDOS_FATPO@INT
          VALUES (:TI_SALIDA-PERNR,
                  :TI_SALIDA-NAME1,
                  TO_DATE(:C_FECHA, 'dd.mm.yyyy'),
                  :TI_SALIDA-DISPO,
                  :TI_SALIDA-SALDOP,
                  :TI_SALIDA-SALDOAU,
                  :TI_SALIDA-SALDOAO,
                  :TI_SALIDA-SALDOAPO,
                  :TI_SALIDA-SALDOAE,
                  :TI_SALIDA-SALDOAD,
                  :TI_SALIDA-DARMC,
                  :TI_SALIDA-SALDOT,
*                :TI_SALIDA-SYSID,
                  :V_FONDO,
                  :TI_SALIDA-ULTIMO_DIV)
        ENDEXEC.
 
    EXEC SQL.
      COMMIT WORK.
    ENDEXEC.

But i have a dump when I run this program, this is part of the dump:


Errores tiempo ejecucióDBIF_DSQL2_SQL_ERROR          
       ocurrido el     07.10.2008 a  14:59:31
------------------------------------------------------------------------------------------ 
SQL error 1722 occurred when executing EXEC SQL.                               
 
-----------------¿Qué ha sucedido?
----------------- 
The error occurred in the current database connection "DEFAULT".               


Other Dump:

Errores tiempo ejecucióDBIF_DSQL2_SQL_ERROR          
       ocurrido el     07.10.2008 a  14:59:31
------------------------------------------------------------------------------------------ 
SQL error 1722 occurred when executing EXEC SQL.                               
 
-----------------¿Qué ha sucedido?
----------------- 
The error occurred in the current database connection "DEFAULT".

How can i do to catch this mistake ?? maybe i can to use catch ... endcatch ¿how can i use it?

Regards

Gregory

Re: DUMPu00B4s with SQL

Former Member — Thu, 09 Oct 2008 21:38:45 GMT

It appears that you are trying to insert a non-numeric into a numeric field.

Rob

Re: DUMPu00B4s with SQL

Former Member — Fri, 10 Oct 2008 02:49:54 GMT

for example.

if PERNR of legacy field is integer and TI_SALIDA-PERNR field is numeric, this program is error.

you have to change legacy field... CHAR or VARCHAR.

Re: DUMPu00B4s with SQL

Former Member — Fri, 10 Oct 2008 05:31:33 GMT

Hi,

I feel, it's not accepting the date format, just check-out with 'SYSDATE'.

regards

Mahesh

Re: DUMPu00B4s with SQL

Former Member — Mon, 13 Oct 2008 13:46:51 GMT

Ready

topic Re: DUMPu00B4s with SQL in Application Development and Automation Discussions

DUMPu00B4s with SQL

Re: DUMPu00B4s with SQL

Re: DUMPu00B4s with SQL

Re: DUMPu00B4s with SQL

Re: DUMPu00B4s with SQL