Hi,

Using a DateTimePicker can give some problems if one changes a part of
the date (month, day, year) that conflicts with the other parts.

I explain: changing the day to 31 when having the month at 02 (feb)
(from previously entered date) will make the caret to stick. This
seems logical, but in Europe we first type the day, then the month: dd/
mm/yyyy. Other conflicts may occur as well, not only this case.

Things get worse if the mindate and maxdate are set: more intermediate
values may result in the control not accepting what you type as i.e.
the month in the year is out of range, but would be in range if the
year is corrected: mindate=2000/06/01, maxdate=2010/12/31, current
value 2000/06/01 -> changing month 06 into 05 would fail, but if the
year was changed first to 2009, then 05 for the month would be OK.

A user can always get out of the lock by changing the conflicting
parts first, but it isn't a logical/quick/easy way to enter data.

One would expect that the validation is done as with a textbox where
when i.e. lost_focus will trigger the validation event.

So, question: is there a way to disable the intermediate validation of
a plausible date until lost_focus (=validate) is triggered?

Using VB2008 Express.


Thanks,


Danny Bosschaerts

0495/23.21.53

Reply via email to