Date:         Fri, 4 Aug 2000 16:35:48 GMT
Reply-To:     bill_kossack@MY-DEJA.COM
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         bill_kossack@MY-DEJA.COM
Organization: Deja.com - Before you buy.
Subject:      Re: bad data in Oracle killing query

SAS crashes out of the query...I was able to pull the information by
using SPSS however that is not a great solution.

In article <8mclim$dfv$1@ctb-nnrp2.saix.net>,
  "Jon" <jont@yebo.co.za> wrote:
> I have also run into a similar problem.  In Oracle the field had a
null
> value, but SAS read it (admittedly it did complain), but reported the
value
> as 17nov1858.  Since the database only started recording data in cc
1985, is
> was an easy task to weed this one out.
> Unfortunately I do not know a work around.  In your case, does SAS
crash
> out, or continue to read data past this point?
>
> <bill_kossack@my-deja.com> wrote in message
> news:8ma5df$gmg$1@nnrp1.deja.com...
> > I'm trying to pull some data from an Oracle table and running into
some
> > trouble.  I have a date field in a table that seems to have bad
data in
> > it giving me the error message...
> >
> > "CLI cursor fetch error: [Oracle][ODBC Oracle Driver]Invalid date,
time
> > or timestamp value."
> >
> > Is there any way around this?
> >
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.