>Thanks for your input, but I design systems to the users' specs.

Even if the specs call for data to be entered in an ambiguous way?

Entering "73" for a year is like enter "SMI" when you mean "SMITH". Fundamentally, it is ambigous and thus is open to error. Your code may interpret the "73" consistently as 1973 (because of the rollover setting) but sooner or later a user will come along that intended "73" to be "2073".

Just passing on my two cents...