date problem.

[Jay Ashworth]

----- Original Message -----
> From: "Richard Kreiss" <rkreiss at gccconsulting.net>

> One of my client's emailed me the other day about a date problem.
> Pfcmark = 20
> 
> Here is the problem, they have member records with birthdays as early
> as the 1920's. However, they also h handle credit cards with
> expiration dates after 2020. This is creating an interesting problem
> in insuring that the dates are correct.
> 
> I realize that I can write some date check logic for wither date.
> Since the doesn't change, It would be easiest to check the birthdate
> on import by setting pfcmark as part of the import routine.
> 
> I am just wondering how one of you might handle this type of issue.

I'm aware that this answer will sound a little snotty, but I'm too tired
to care.  :-}

"Do the work you should have done 17 years ago: convert all date fields
to MDYY/, and make sure all intermediate dummies are big enough and that
all code that touches them makes no intemperate assumptions about their 
type."

Why do I know that?

Cause I did it all, 17 years ago.  For about 20 clients.

Those were halcyon days... :-)

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates       http://www.bcp38.info          2000 Land Rover DII
St Petersburg FL USA      BCP38: Ask For It By Name!           +1 727 647 1274