When using SAS/ACCESS Interface to ODBC with Microsoft SQL Server, you might get incorrect dates of 01JAN1753. The following example shows the problem:

    libname anlanldb odbc dsn=your-dsn user=user-ID password=password bulkload=yes;

    proc sql;
       drop table anlanldb.petetime;
    quit;


     data anlanldb.petetime;
       format c d e datetime23.3;
       c='31OCT2015:00:00:00.000'dt;
       d='31MAR2015:00:00:00.000'dt;
       e='29MAR2015:00:00:00.000'dt;
       put c= d= e=;
     run;
     proc sql ;
        select * from anlanldb.petetime;
     quit;

You receive the results shown below. (Note the result for variables d and e.)

c d e
31OCT2015:00:00:00.000 01JAN1753:00:00:00.000 01JAN1753:00:00:00.000

The problem occurs with version 14 of the Microsoft ODBC driver and when the option BULKLOAD=YES is specified in the LIBNAME statement.

To circumvent the problem, do one of the following:

• Create a data source name (DSN) from an earlier version of the Microsoft ODBC driver for SQL Server. (Multiple versions can be installed on the same machine.)
• Remove BULKLOAD=YES from the LIBNAME statement. You can use INSERTBUFF=1000 READBUFF=1000 to increase the performance on your LIBNAME statement.

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to ODBC 9.4_M3 is available at: