The behavior is by design, during DayEvents-OnClick the selected value has not been applied to the WebInput. In order to determine the WebInput that triggered the event and the currently selected date, you could use the event parameter. Here is the snippet:

function UpdateDates(ctrlId, selectedDay, selectedMonth, selectedYear) 
{
    var currentInput = ISGetObject(ctrlId);
    
    var dataCaptureDate = ISGetObject("wiCaptureDate");
    var webInput1 = ISGetObject("WebInput1");
    var webInput2 = ISGetObject("WebInput2");
    var strMessage = "";
    var selectedDate = new Date();
    selectedDate.setFullYear(selectedYear, selectedMonth - 1, selectedDay);
    strMessage += "Current input:" + selectedDate.toDateString() + "\r\n";   
    if (ctrlId != "wiCaptureDate")
        strMessage += "Data Capture Date:" + dataCaptureDate.GetValueData() + "\r\n";
    if (ctrlId != "WebInput1")
        strMessage += "Web Input1:" + webInput1.GetValueData() + "\r\n";
    if (ctrlId != "WebInput2")
        strMessage += "Web Input2:" + webInput2.GetValueData() + "\r\n";
    alert(strMessage);
}

Glen,

The problem isn't so much with the DayEvents-Onclick event, it is with trying to retreive a value from the control with any event from any function, even from the controls that didn't trigger the event.

Also, I am setting the values of the Date Controls in the Code Behind page, not in client side script so when the controls display they show the correct values, I simply can't retrieve them with your API.

However, if I move the same controls to a standalone ASPX both, both versions that I have supplied work fine, so to me this is a bug.  So if this is "by design" how come the same code works differently in a  a StandAlone ASPX page.  Sample is attached, have a look at the "StandAloneWebInput.aspx" page which works just fine with the same code, however inside a Master Page, user control, it does not work.

In this sample I have provided I have even tried to call the UpdateDates method from the "body.Onload" event. 

I have also tried looking at the script in the debugger, the WebInput control simply does not return the value unless you use the initial workaround I supplied.  

Regards,

Adrian.