Aloha!

I'm currently working with the Q3 2009 version of the ASP.NET controls and seem to have hit an oddity with the RadDatePicker (and probably other) controls when setting the EmptyMessage and performing optional field validation.  I've set the EmptyMessage on the control and also have a RangeValidator applied to it; validators don't typically validate empty text and this is fine on the client validation (no error) but server-side fails as the ValidationDate is set to the EmptyMessage value, causing the RangeValidator to try and validate.

Is there a way around this, short of making code changes and performing custom validation, enabling/disabling validators etc?  Or should I just remove the EmptyMessage value?  I've read a couple of other threads here discussing always catching the (possibly invalid) data entered in ValidationDate but in this case, there is no explicit data entry.

Thanks in advance.

Kev.

Hello Kev,

Indeed, currently there is a problem with this scenario, which we will research and do our best to fix for the next release. The easiest workaround is to remove the EmptyMessage. For example you can use a label in front of the control. Sorry about the inconvenience.

I have updated your Telerik points for bringing the issue to our attention.

Sincerely yours,
Dimo
the Telerik team

Thanks for the response - at least I know I'm not going crazy or doing something stupid (or both!)  I've removed the EmptyMessage settings for now.  Here's looking forward to the next release :)

Hello Kev,

The problem has been fixed, so you can try the next RadControls internal build, once it becomes available (some time next week).

http://www.telerik.com/account/downloads/internal-builds.aspx

Greetings,
Dimo
the Telerik team