When typing in a date in the UltraDateTimeEditor the value changed event is firing as soon as you type in the first digit of the year. This causes the date to be set in the control. I tested against Net Advantage 2009.1 and also the Service Release 2039.
To test create a winform drag a date time editor onto the form subscribe to the value changed event and put a break point on the event. Run app and type in a date. As soon as you type the first digit for the year part the event fires and sets the date.
This is only a problem if you subscribe to the value changed event.
This is the intended behavior. Whenever you type into the control, it calls Date.Parse and tries to turn the text into a date. Date.Parse will return a date if you enter a single digit, so the control's value changes.
This was not the behavior of this control in the 2008 .net 2.0 version.
We recently upgraded to 2009 controls and this has caused breaking changes at RunTime in our application.
I can change from using the ValueChangedEvent to AfterExitEditMode and all is fine.