Last post Jul 07, 2006 04:05 PM by Rica0625
Jun 16, 2005 05:40 PM|aspNewB|LINK
Jun 23, 2005 12:10 PM|stevenbey|LINK
Hi there and welcome to the ASP.NET Forums.
The ASP.NET Calendar Control is purely a server-side control and so requires a PostBack in order to store the SelectedDate(s). There is no other mechanism to store this/these values.
The BasicDatePicker, on the other hand, uses client-side code to insert the SelectedDate into an associated TextBox and also uses client-side code to re-render the calendar when navigating to the previous/next month.
A solution that I have used in the past is to place the ASP.NET Calendar Control in its own page, which is called inside an
Jun 23, 2005 08:55 PM|subdigital|LINK
Jun 24, 2005 04:12 AM|stevenbey|LINK
In response to the iframe solution above, IFRAME will be deprecated tag pretty soon, won't it? I wouldn't want to implement any functionality that I thought would be unsupported in the future... but I could be wrong ;)
Jul 07, 2006 11:34 AM|Terrahawk|LINK
Jul 07, 2006 04:05 PM|Rica0625|LINK
I have this calendar component. This is free. This component no execute the postback when select a date.
Include this html meta tag in your page.
This eliminate the flicker in the postback. (IE)
<meta http-equiv="Page-Enter" content="Alpha(opacity=100)"> <!-- Remove the IE Flashing -->