× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This somehow sounds date format/date window related.  It's a lot like the
problems I've caused for myself more than I'd like to admit with mmddyy
screen fields and yyyymmdd database fields.

> -----Original Message-----
> From: Fisher, Don [mailto:Dfisher@roomstoreeast.com]
> Sent: Monday, January 07, 2002 1:23 PM
> To: 'midrange-l@midrange.com'
> Subject: Re: SQL Error -183
>
>
> Curiouser and curiouser.
>
> On a hunch I changed the "field in error" to "1940-01-01" and
> executed the
> program.  The SQL error disappeared.  I then changed the value to
> "1939-12-31" and the SQL error reappeared.
>
> The field in question is a DATE field using the *ISO format.  The
> documentation clearly states the valid values are between
> "0001-01-01" and
> "9999-12-31".
>
> So am I missing a PTF or misreading the documentation?
>
> Donald R. Fisher, III
> Project Manager
> The Roomstore Furniture Company
> (804) 784-7600 ext. 2124
> DFisher@roomstoreeast.com
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.