Re: SQL Error - Data Type Has Changed?

[Randy Learn <rlearn@UAKRON.EDU>]

The record your program is bombing on may have a null value in the
linecost
field.  This may cause it to bomb when multiplied by 100.  I believe there

is a null value function in Oracle which you could use to convert the null

to 0 before multiplying by 100.

C. Duncan Hudson wrote:

> > In the snips, I observed one typo. Could it be the
> > reason?
> >
> > In select statement,
> > where invoicenum = &invoicenum
> > In error_proc,
> > display 'Invoice = ' noline
> > display &_invoicnum
> > Are &invoicenum and &_invoicenum same?-Raju
>
> Yes, &invoicenum and &_invoicenum are the same thing.  &_invoicenum is
> used in the error_proc to denote that it is a global variable and not
> a variable local to the procedure.  That aside, by the time I reach
> the error_proc procedure the SQL error has already occured.
>
> Dunc
>
> _________________________________________________________
> DO YOU YAHOO!?
> Get your free @yahoo.com address at http://mail.yahoo.com