Re: SQL Error - Data Type Has Changed?

["Mosley, Banessa" <Banessa_Mosley@MAIL.CI.BALTIMORE.MD.US>]

If a null value is your problem, I believe the null value function in
SQR is nvl.  The syntax will be as follows:

nvl(&invoicenum,'',0)

In this scenario, SQR will replace a null value in &invoicenum to a 0.

I hope this is correct.  If not, please let me know.

Banessa Mosley
Business Information Technology

> -----Original Message-----
> From: Randy Learn [SMTP:rlearn@UAKRON.EDU]
> Sent: Wednesday, July 22, 1998 10:51 AM
> To:   Multiple recipients of list SQR-USERS
> Subject:      Re: SQL Error - Data Type Has Changed?
>
> 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