>>>>>>I think I'll just go with the flow and force the users to enter the extra two digits.
>>>>>Not quite right. Despite the fact that four digits are shown, the user can still enter one, two, or four digits. This was true even if you SET CENTURY ON in FP 2.6. The user could enter a one or two digit year; FP would interpret it as 19xx, and display the four digits. (It shocked me when I found this out, but I tested it and it's true.) Note that this is NOT true in VFP6 if you SET STRICTDATE to 1 or 2. But if you set STRICTDATE to zero, it acts like previous versions did, allowing entry of any number of digits up to four for the year.
>>>>>
>>>>>Cheers,
>>>>
>>>>That's fine, I knew about the two digit entry still working - very interesting that 1 and 3 work, that's cute. But, hey, we are talking about users here :-) - if they see 4 digits that's what they'll type.
>>>
>>>Not MY users! Where do you get users who actually look at what they're typing into? :)
>>
>>Ahhh... most of my date fields are pre-loaded with a default or existing dates. So the user has to type over all the digits anyway. Anyway if I could understand how the users thought I wouldn't be a programmers bootlace :-)
>
>I usually have all my textboxes SelectOnEntry=.T.. So if they start typing a date in, the old date disappears, and once again they can type in as few digits for the year as they please. Maybe I should SelectOnEntry=.F. for all dates ... but I think most of my users would balk at this.
>
Hmmmm... probably the most common use for date entry is to specify a date or date range for a report. Mostly, in my systems a sensible default date is already there, so they might only wish to change the day. So generally I prefer SelectOnEntry=.F. and the users do too. But of course it depends...

Regards