Using Calendar1_SelectionChanged to create SqlParameter

Question

I'm having trouble getting my SqlParameter to work in my SqlDataSource select command. I'm trying to run a query when a new calendar date on a calendar control is selected to filter the query by the date selected. Here's what I have on the C# end:

protected void Calendar1_SelectionChanged(object sender, EventArgs e)
{
    SqlParameter para1 = new SqlParameter("@mydate", SqlDbType.DateTime);
    para1.Value = Calendar1.SelectedDate;
    SqlDataSource1.SelectParameters.Add(para1);
}

I /almost/ found what I need via this thread: How can I set the sqldatasource parameter's value?

but the solution offered by the top answer gives me the following error for the SelectParameters.Add line: "The best overloaded match ... has some invalid arguments."

How can I fix this error and get the parameter to work in my select query?

Thanks.

What's the value for Calendar1.SelectedDate when this event fires? — jordanhill123
– jordanhill123, Commented Mar 6, 2013 at 13:45
When the page loads the calendar is set to today's date in this format: 3/6/2013 12:00:00 AM — erstaples
– erstaples, Commented Mar 6, 2013 at 13:58
Might sound silly, but can you confirm that Calendar1.SelectedDate is returning a DateTime object? — freefaller
– freefaller, Commented Mar 6, 2013 at 14:24

Community · Accepted Answer · 2017-05-23 12:27:15Z

1

Per the comment in regards to Jon Skeet's answer on this link: Setting DateTime as a SqlDataSource parameter for Gridview, try changing this line to

para1.Value = Calendar1.SelectedDate.ToString();

and see if that works.

Edit Per comment from jadarnel27, try the following:

SqlDataSource1.SelectParameters.Add("@mydate", SqlDbType.DateTime, Calendar1.SelectedDate.ToString());

As SQLParameter.Value is of type object, the overload may be doing some validation on the Calendar1.SelectedDate.ToString() to match with the SQLDbType

edited May 23, 2017 at 12:27

CommunityBot

11 silver badge

answered Mar 6, 2013 at 14:12

jordanhill123

4,2032 gold badges33 silver badges40 bronze badges

Sign up to request clarification or add additional context in comments.

9 Comments

freefaller Over a year ago

As much as I hate to even contemplate going against Jon Skeet... I cannot see the logic in turning a date object into a string representation. There's just too much to go wrong when converting back to a date object

Josh Darnell Over a year ago

@freefaller Jon Skeet is saying not to convert from DateTime to string in the linked answer (so agreeing with what you say). jordanhill123 here is referring to the comments by the OP of the other question below Skeet's answer that say they had to convert to string, because the DateTime wasn't valid as a parameter to the method he was using.

jordanhill123 Over a year ago

@freefaller I don't see the logic either but not sure where else its going wrong. It worked for the OP but I don't like it either...is it possibly something with its use in asp.net or maybe the specific calendar implementation? Just wanted to test to see if it works

Josh Darnell Over a year ago

And the OP here might be better off using the overload that Jon used in the linked question: SqlDataSource1.SelectParameters.Add("@mydate", SqlDbType.DateTime, Calendar1.SelectedDate.ToString());

freefaller Over a year ago

Fair enough guys (@jadarnel27) - didn't quite follow exactly what was going on. my only guess is that this calendar control isn't returning a .net standard DateTime object

|

Collectives™ on Stack Overflow

Using Calendar1_SelectionChanged to create SqlParameter

1 Answer 1

9 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

9 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related