DSXchange

Thanks guys. Hardcoding the date led me to discover that the date format expected at the SQL Server target was yyyy-dd-mm and not yyyy-mm-dd as per the dataset and this is what was causing the arithmetic overflow (not the microseconds as first thought). Just find it annoying that the Enetrprise ODBC...

Apologies if already answered but I couldn't find it anywhere. I have an issue whereby that I am trying to load from a dataset to a SQL Server 2005 table using the ODBC Connector. All works fine until I try and load a timestamp (26,6) into a SQL datetime (23,3) - I then get an Arithmetic Overflow ab...