>>>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...

Yes, I'd say that's my most common use for them, too. And I also usually have a default filled in. Which is exactly why my users have requested over and over to have SelectOnEntry=.T., because if they tab there and start typing, they want the default to be replaced. Most of my users, than select the day or the month and type over it, prefer to type the whole date. Because that's faster for a "heads-down data entry" type than reaching for the mouse, or fiddling with shift+arrow to highlight.

Obviously each user/client will have different requirements. And you, like me, just keep givin'em what they want! :)

Drinking a stout in your honor right now. (Brewed by Traverse Brewing Co. in my home state of Michigan.)

Cheers,