My users have been reporting since yesterday that dates they enter into the WebDataGrid are losing a day when saving to the database.

On closer inspection, these date/time fields are losing 1 hour.  For example, if a user enters 11/7/2011 into the WebDataGrid, 11/6/2011 11:00PM will be stored to the database, and the users then sees 11/6/2011 displayed in the grid as his saved value.  This occurs regardless of the EditorProvider used...  This even happens if you use the TextBox provider.

And this began recently, oddly corresponding to Daylight Savings Time.

I have found a very clumsy workaround.  If you change your SQL statement so that it converts DateTime fields to VarChars, the WebDataGrid won't corrupt the date.

I have opened a support ticket CAS-77072-NSTXZT, but have also posted the issue and the workaround here, for the benefit of other users.

I consider this issue to be critical, since it is corrupting data.