Accepting 2 digit years does conflict with data integrity. There are at least three commonly used interpretations of 01/02/03 (is it 2001-02-03 => YY/MM/DD or 2003-02-01 => DD/MM/YY or 2003-01-02 => MM/DD/YY ?) (And when you include uncommon formats it gets worse.) Being liberal in what you tolerate doesnt mean you have to tolerate totally ambiguous input.

Beside the lawsuits Id be thinking of all the hassle of cleaning up the data when you get an American in the office (or any nationality NOT the one you are designing for.)

Anyway, i'll let it rest now, and hope you realize I said all of this in the best of intentions. :-)

Regards,

---
demerphq

_{<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...}