Hi,

With Q2 2011 DateTimePicker if I set the NullDate to DateTime.Today.AddSeconds(1) I can not set the date to today's date as it shows up blank (null) as soon as I choose todays date. If I choose the day before or after today it works.  Did something break in this version or am I missing something?  Also, it would be nice if by default if the user hits the delete key anywhere within the date text that the value is set to null and the textbox is cleared.  It is a problem to our users when the delete button is hit in the year field and it just changes to 0001 as in your examples.

I followed this thread to set nulldate to today to avoid having the calendar show or 0001 for the year. http://www.telerik.com/community/forums/winforms/calendar-and-datetimepicker/setting-mindate-but-not-value.aspx

Thanks!

Hello David A.,

I can confirm the issue.

We will address this misbehavior in our SP release at the end of August. We have added points to your account for the report.

I would like to inform you that in Q2 2011 we provided support for Null Value in RadDateTime/RadMaskedEditBox. So, the following code should show an DateTimePicker with "Enter Date" text:

Do not hesitate to contact us if you have other questions. Greetings,
Peter
the Telerik team

Hi, 

I have a question for Peter, would NullableValue be the correct property to bind data to? Does it accept DBNull.Value as well?

Thanks for your time.

I was unable to bind via dataset to NullableValue.  I had to subclass the control and add a property called "BindableValue" to work with DBNull.

I was working around this problem yesterday and decided to have the controls Binding object do the conversion by setting its NullValue during initialization.

 I posted more detailed explanations here :
http://www.telerik.com/community/forums/winforms/calendar-and-datetimepicker/raddatepicker-and-null-values.aspx#1747985
and here:
http://www.telerik.com/community/code-library/winforms/editors/nullabledatetimepicker.aspx#1748021

Interesting posts hartley.  Will that set "ClientSinceDate" to DBNull through databinding without a date value?

Yes, the "ClientSinceDate" value in my SQL Server table becomes <null>, when the record is saved, so the data table value must have been set to DBNull. This will happen when you press the Delete key in the control.

I set the Binding's NullValue and the DatePicker's NullDate to the same value. So the binding changes DBNull into NullDate when it sets the value, and changes NullDate into DBNull when it receives a value.

Remember to set this Databinding in the code file, not the designer file. Visual Studio will overwrite it if you make any changes to the form.

Hello everyone,

Thank you for writing.

Getting straight to the questions, we do not support DBNull value at the moment because DBNull.Value cannot be assigned to NullableValue property (of type DataTime).

The upcoming Service Pack will contain improvements in the binding logic which will make NullableValue the correct property to bind data. We also plan to improve the NullableDate: RadDateTimePicker will check only the Date part of this property and ignore the Time part. I will be happy to hear any comments or concerns that you might have about this change.

I hope you find my answer useful. Let me know if you have further questions.

Greetings,
Peter
the Telerik team

Hi Peter,

I look forward to these changes. 

In order to handle a DBNull I inherited the control and added a bindable property (BindableValue) of type object.  The other two issues that I have with this control is when hitting the delete key in the year field makes the year 0001 (or mindate year) and hitting delete in month/day sets it to 1.  I prefer to have the control set to null if delete is hit at all in the control:

When the value is null and the user clicks the drop down, the calendar displays the mindate.  This has been discussed on other threads, but my solution was this:

It would be ideal if something like the above was implemented in the service pack or a future release.  I greatly appreciate your concern.

David A.

Hello David A.,

Thank you very much for the suggestion.

We will do our best to implement this behavior in one of our next releases.
I think that this behavior should be switched on and off by a property, because this will be a breaking change for the users.

I have updated your Telerik points for the cooperation.

Best wishes,
Peter
the Telerik team

Hello David A.,

I would like to inform that we improved this behavior in Q1 2011 SP1. Feel free to download this version from Your Account and give it a try.

Regards,
Peter
the Telerik team