Did you ever find a solution?

I have been getting the same thing and I saw a thread that I found by searching GOOGLE, that said the new ODBC driver was the problem. I have not been able to find an older version. The version I have is 3.51.10 and it gives me the same messages you get.