Stuart McLachlan
stuart at lexacorp.com.pg
Wed Jun 6 07:03:34 CDT 2012
And it was 18 June 2011 when he fought with it the first time. At that time I posted this: ------------------------------------------------------------------------- http://msdn.microsoft.com/en-us/library/ms180878.aspx#ODBCDatetimeFormat <quote> Backward Compatibility for Down-level Clients Some down-level clients do not support the time, date, datetime2 and datetimeoffset data types added in SQL Server 2008. The following table shows the type mapping between an up-level instance of SQL Server 2008 and down-level clients. </quote> Looks like you are using one of SQL Server 2008's new date/time data types for that field and accessing it via ODBC. MS in their wisdom have decided to convert it and return a YY-MM-DD string instead of a numeric value of some type. Best bet is to change the field type in SQL Server to one of the older datetime or smalldatetime types. ------------------------------------------------------------------------- Guess some people never learn :-) -- Stuart On 6 Jun 2012 at 13:48, Gustav Brock wrote: > > It was Feb. 17th you fought with this the last time. > > /gustav > > -- Stuart McLachlan Ph: +675 340 4392 Mob: +675 7100 2028 Web: http://www.lexacorp.com.pg