We Keep Coding

How to restrict text entry on Kendo Angular Date Picker?

Kendo's Angular Date Picker, restricts the date selection using [min] and [max] to select date from the UI. However, for text entry (user types in the date instead of selecting from the datepicker) user is restricted to enter months above 12 and dates above 30/31 accordingly. But, I need to restict user to type the year as well. Suppose if user types 1996 and my max year is 1995, the date year should change to 1995.

You can make one function which triggers when date is changed, this function should check if your requirements are satisfied with newly entered date OR it should revert back to last value . The Benefit of this approach is that user still can type the values but still it should be inside your validation range.

Xaml DatePicker default and earliest date available for selection settings in C#

I have couple of datepicker implemented in Xaml .
- After user picks certain dates, a simple logic finds the earliest of the two dates. Also, it is not necessary for user to pick both dates.
I noticed that the "default" datepicker value if user does not pick any date is 1/1/0001.
Assuming the user picks the second date as 1/1/2017, the earliest of the two dates would always be 1/1/0001 which is not desired. In such scenario, the minimum date should be 1/1/2017.
what is the logic to neglect default date of 1/1/0001

There is a property MinYear which can be set to minimum year accepted which in your case obviously should be 2017. This will solve the problem by automatically limiting range of available values to be lower bounded by 2017-01-01 - this for UWP DatePicker.
In WPF DatePicker there is a DisplayDateStart property which can be set to minimum date available in drop down calendar which can be chosen by user. Similar property DisplayDateEnd is used for setting highest date which can be displayed in DatePicker. DatePicker.SelectedDateChanged is a very useful event which when wired up will capture changes to the dates on all instances of DatePickers and this can be used to create relations between them i.e. to enforce selection of the valid period which starts from date selected on DatePicker 1 and ends on date selected in DatePicker 2 by setting DisplayDateStart on picker 2 to date selected on picker 1 in event handler. This all together provides very high level of flexibility in controlling user input via DatePicker class.

Change value of DateTimePicker

I'm having problem to change the displayed value of my DateTimePicker object in C# Winforms
I'm trying to change the date in the DateTimePicker according to the value, but the display won't change.
dtpDisplayTo.Value = DateTime.Today;

I know this is dated, but I just had the same problem and found a solution with a bit of research. You have to set the Checked property of the DateTimePicker to True before changing the date, otherwise the control will consider the change as null and not show the new date. Really strange stuff.
DateTimePicker displays today's date instead of displaying its actual Value

Take the datepicker value

i have a gridview that dynamically generate datepicker , i have taken the value of datepicker using
GMDatePicker dtp = (GMDatePicker)Gridview1.Rows[rowIndex].Cells[3].FindControl("frmdate_starttime");
and i have inserted using dtp.Date,while storing in the database it only store the date and not the time. how to retrive the time to save in database along with date

You can change the Format property to Custom and the CustomFormat property to what you require, something like dd MMM yyyy hh:mm.
You should then be able to use
DateTime dt = dateTimePicker1.Value;
to get the date and time.

Split the problem into two parts: are you getting the right value out of the control but failing to save/restore it in the database correctly, or are you failing to get the right value out of the control in the first place? Once you've worked out whether it's a UI or database problem, you can ignore the other half of it.
Have you enabled the time picker in the control?
What column type are you using in the database?
If you run your application in the debugger, what value do you see before you store it in the database?
If you run a query against the database in the relevant admin tool, does that show a time?

DateTimePicker displays today's date instead of displaying its actual Value

We have a couple of DateTimePickers on a custom UserControl, on a Form. They are visible, but not enabled (for display purposes only). When the UserControl is loading, the DateTimePickers are assigned values from a DataRow that came from a DataSet which stores a single record returned from a SQL Server stored procedure.
There is an inconsistent behavior in which the users sometimes see today's date instead of the date that was assigned to the DateTimePicker. It doesn't seem to matter whether I assign the date I want to the .Value property or the .Text property:
txtstart.Value = (DateTime) dr["Group_Start_Date"];
txtend.Text = dr["Term_Date"].ToString();
I expect that of the two statements above, the one using the Value property is more appropriate. But, in both cases, today's date is displayed to the user regardless of the values that were in the database. In the case of txtstart.Value, Visual Studio shows me that the value was assigned as expected. So why isn't it displaying that date to the user instead of today's date?

I found the answer. You MUST set the checkbox value to checked to indicate a non-null value.
this.dateSold.Checked = true;
// set to true or false, as desired
this.dateSold.ShowCheckBox = false;

I was having trouble with this too and found that you indeed need to set the .Checked value to True.
I set the Checked property in the properties window and it still didn't work so I just set it in code before assigning the value and that fixed the problem.

It seems to be a problem with having multiple DateTimePickers. I was able to get around the issue (bug?) by programatically creating the DateTimePickers with the values I wanted and adding them to the form.

I ended up going with AB Nolan's suggestion. The reasoning behind a disabled DateTimePicker was never clear to me, so back on 10/23/2009, rather than continue fussing with the control I just displayed the dates I wanted in TextBoxes instead.