×
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.
On Wed, Mar 4, 2015 at 10:47 AM, Cyndi Bradberry <CyndiB@xxxxxxxx> wrote:
Yup, chose the 4 digit year to store and display (*ISO & *USA) specifically to avoid the issue with 2039.
You may have been responding to Rich, who seems not to have received
Scott's or Chuck's posts at the time that he responded.
In case you yourself also missed those posts, what Chuck tried to
explain is that the data has to pass "through" SQL on its way from the
disk to the screen, so even if the field on disk and the field on
screen are "big enough", the temporary storage in SQL may not be. So
Scott and Chuck mentioned that you have to set the SQL environment's
date format to an appropriate type, to accommodate the transfer of the
full 4-digit year.
John Y.
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.
midrange.com
