I am exasperated with this control beyond belief. I cannot believe a company
with the resources of Microsoft could release something so bad that it is
unfixable. The cynic in me says that this was done by design -- to drive
developers to spend their days trying to fix something unfixable rather than
to move onto something productive. I've tried everything to make it work
with binding, including some solutions recommended by others (i.e., the
parse and format handlers). Simply put, over the course of several months,
I've revisited this issue over and over and have found NO real solution.

</end rant>

What I need is a control that can truly be bound. A control that doesn't
accept the first value but drop the next. A control that doesn't fake you
out by showing one value but saving null or an empty string. A control that
handles nulls. A control that doesn't require a goofy checkbox for no date.
And ideally, a control that I can buy separately without an entire IDE of
controls. Anyone?