> As long as the user enters a full, 4-digit year, yes, this should work.
>
[quoted text clipped - 13 lines]
> >>
> >> Simon Webb
No, not per my testing. If for example, you enter
4/02
the value stored in the table is actually April 2, 2005 (for my US system).
If you enter 3/98, the value stored is March 1, 1998; I assume the
difference is because ACCESS knows that no month has 98 days.
The confusion appears to result if the "second" number is 31 or less,
obviously depending upon the month number for the "first" number

Signature
Ken Snell
<MS ACCESS MVP>
> What problem would you forsee if the user entered a month/2-digit year?
> Wouldn't this be interpreted, as requested by the OP, according to the
[quoted text clipped - 22 lines]
>> >>
>> >> Simon Webb
MacDermott - 31 Jan 2005 12:02 GMT
I stand corrected. Apparently I hadn't tested enough.
> No, not per my testing. If for example, you enter
> 4/02
[quoted text clipped - 33 lines]
> >> >>
> >> >> Simon Webb