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

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Issue with dates in SQL -- errors under some conditions, but not others.
From: Sam_L <lennon_s_j@xxxxxxxxxxx>
Date: Tue, 26 Feb 2013 19:06:07 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.