× 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.


  • Subject: Re: Y3K or not to Y3K
  • From: Glenn Ericson <Glenn-Ericson@xxxxxxx>
  • Date: Sun, 06 Feb 2000 14:52:21 -0500

At 05:53 PM 02/06/2000 GMT, you wrote:
 >An interesting question was just asked here.  Why, on a brand new
 >application with no dates prior to Jan. 1, 2000 are we using an 8-digit
 >date?  L-Date fields are not relevant  -  this is an *M36 installation and
 >likely to remain so.
 >_______________________
 >Booth Martin
 >boothm@earth.goddard.edu
 >http://www.spy.net/~booth
 >_______________________
 >
 >+---
 > Booth  I  have no-clue.  Just a few thoughts.

Is the application design underneath  rely on  8 digit dates?

Do external interfaces/infrastructures seek  that format?

Is it a package  application, perhaps designed for universal
implementation  before during and after  01-01-2000?

Maybe the  disigner had to certify Y2K compliance,
regardless of   this  clients needs ?


________________________
Glenn Ericson,
Phoenix Consulting LLC
Ph.(718)898 9805  Fx .(718)446 1150
mailto:Glenn-Ericson@att.net
__________________________ 

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.