The basic problem here is assuming that just having an ODBC driver is enough to accurately convert rather different data types seamlessly between Oracle and SQL Server. The differences are too large for such a simplistic solution, and as the connectivity passes thru ODBC, which only supports a subset of the data types of either SQL Server or Oracle, imperfections are going to happen. There really can't be a one-size fits all solution to the problem, either. Dates are the biggest piece of grief, as numeric data can at least be CAST or CONVERTed to the right type. FYI...