Re: Issue with dates in SQL -- errors under some conditions, but not others.

[Sam_L <lennon_s_j@xxxxxxxxxxx>]

Change your session attributes in STRSQL with F13 and set the date 
format to *ISO, or something that supports a 4-digit year.  Generally in 
the USA the default is *JOB, which is generally MM/DD/YY and you can't 
represent 0001-01-01 in that format.

Sam

On 2/25/2013 8:25 PM, James H. H. Lampert wrote:

> If we look at the VIEWs that use this in QuestView (i.e., via native
> record-level access), any zeroed-out fields show up as January 1st of
> the year 0001, as designed.
>
> But if we look at it in STRSQL, those same zeroed-out dates come back as
> a field of plus-signs.