Jim Meagher
=====
Micro Solutions Consulting     Member of The HTML Writers Guild
http://www.ezy.net/~microsol   International Webmasters Association
=====
-----Original Message-----
From: Earl Truss <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Sunday, March 22, 1998 1:03 AM
Subject: Re: [PCSOFT] Year 2000 Compliance


>At 09:25 PM 3/21/98 -0500, you wrote:
>
>It is easy to say something is Y2K compliant ... but what
>exactly does that mean?
>

It means that if given the proper information, the program/application
can accurately deal with dates above and beyond the year 2000.

>
>One problem I run into all the time in Access is
>the "pivot year" problem.  If one is not careful with formatting
dates,
>when someone enters a two-digit year, Access will interpret dates
before
>"30" as being in the 21st century instead of the 20th century.  This
is
>always a headache for me when dealing with birth dates ...
>

That's a database design problem not an application flaw.  If you
don't give the program enough information, then you can't expect it to
reach a valid conclusion.  Redesign your forms to include an input
mask and validation rule that require a four digit year and you won't
have problems.