I am using an UltraCalendarCombo with a MinDate set to Date.Now. If I try to select yesterday though, the UltraCalendarCombo is set to "(none)." This occurs even if I have the AllowNull property set to false.
Edit: Setting the mindate to Date.Now also disables today as well as the previous dates. It is when I try to select today that the UltraCalendarCombo display text is being set to "(none)" and the value is being set to String.Empty. This occurs even if the property AllowNull is set to false.
Hello Bryan,
I tried this and it always works fine for me so I attached my sample to this post for you. Please review it and feel free to let me know if I misunderstood you or if you have any other questions.
I am unable to run your example as my company is currently running NetAdvantage 11.2 Win CLR2x. Could this be a bug that has been fixed between the version we are running and the latest version?
I tried with your example and I get the same result. I checked my question though and realized that I misspoke earlier. Setting the minvalue to Date.Now will disable all dates leading up to and including today's date. It is when trying to select today's date that the value is being set to String.Empty and the display text in the UltraCalendarCombo is set to "(none)." Do you get this same result?
I will edit my original question and correct it.
Hello,
Thank you for the clarification.
I believe that you should use 'DateTime.Today' rather than '.Now', since 'Now' means that the day has already started and it counts it as a past day. Do you agree on this?
This fixes my issue, thank you.
Out of curiousity, since DateTime.Now is being counted as a past day, shouldn't it be handled the same as the other past days instead of setting the UltraCalendarCombo value to String.Empty, or is there a reason for this?
It is a reasonable question and after some research I think that is made because there should be a way to distinguish the different states in the calendar - past(denied, future(allowed), partially past(denied). If you think that this should be handled in another way, I could start researching a workaround and/or contact our engineering staff to review this behavior.
I'm just not sure I understand the need for handling partially past dates differently from past dates. The partially past date is denied which prevents the user from setting the UltraCalendarCombo to that date. If the user isn't allowed to set their UltraCalendarCombo to that date, then I believe it should be handled the same as the other dates that are denied.
Admittedly, just because I can't think of a reason for this behavior, doesn't mean there isn't one. This is simply my opinion.
I created the following case for you: 'CAS-100914-Y9Y7P1' and will update you through it.