From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_20,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,92471489ebbc99c6
X-Google-Attributes: gid103376,public
From: eva_remove_this_ns@evans.pgh.pa.us (Arthur Evans Jr)
Subject: Re: Y2K Issues
Date: 1998/10/28
Message-ID: <eva_remove_this_ns-2810981000420001@ppp42.s9.pgh.net>#1/1
X-Deja-AN: 405947831
References: <362B53A3.64E266AB@res.raytheon.com>
 <36365724.EF1CC215@maths.unine.ch>
Organization: Ada Consulting
Newsgroups: comp.lang.ada
Date: 1998-10-28T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <36365724.EF1CC215@maths.unine.ch>,
Gautier de Montmollin <gautier.demontmollin@maths.unine.ch> wrote:

> Someone in an hydrological bureau had the same shock today reading that
> LRM topic in AdaHelp, but because of the 1901 problem: many archived time
> series begin before 1901... (hydrology, geography etc.) => Calendar is
> useless for it !

The problem is also important for genealogical research, in which dates
hundreds of years in the past are needed.  I've long represented dates
in genealogy records as YYYY.MMDD, usually in a text field.  Note that
dates so represented sort properly, whether stored as text strings or as
decimal numbers.

Art Evans

Make the obvious fix to my address to reply to me.