This is a known issue with Data Direct ODBC driver. There is a registry update for that DSN that you need to do in order to get past it. You need to create a new key called WorkArounds2 and set it o 8192.
I am having the same problem. I had already tried creating the WorkArounds2 key with 40960 that I found in a different forum. It didn't work. I just tried this value and it didn't work either. Any ideas?