Gustav Brock
gustav at cactus.dk
Wed Jun 6 06:48:45 CDT 2012
Hi John "Stopped all that"? So now you handle your date values as strings? Oh my ... And a "time() format" ... what is that? Unless you need the submillisecond resolution SQL Server data type DateTime2 offers, all you need is to change the data type (not a format) of the field in SQL Server to good old DateTime. Then your framework will run unmodified. It was Feb. 17th you fought with this the last time. /gustav >>> jwcolby at colbyconsulting.com 06-06-12 5:48 >>> I know! My memory is getting really bad. I knew that was the problem but when I made the change (in SQL Server) it didn't help. It turns out that my framework was determining that the control's data source was a date and putting in a date format string. Once I stopped that it all started working. John W. Colby Colby Consulting Reality is what refuses to go away when you do not believe in it On 6/5/2012 11:15 PM, Stuart McLachlan wrote: > I seem to recall having the same discussion about a year ago where we identified the > problem with the new SQL Server Date and Time types and ODBC returning them as strings > :-)