I haven't seen that exact error before, however, one thing I'd suggest is to avoid using ODBC unless it is absolutely necessary for that particular data source.

If you're connecting to a SQL database, you're going to get much more reliable performance with a direct connection, and then you could used named parameters (@name) instead of the ?

Again, I wouldn't assume it is related to your error, but using ODBC for SQL databases in Workflow just adds an unnecessary middleman (i.e., one more thing to break/troubleshoot).

If you're already using that data source for other processes, be careful about changing the settings because any queries set up with ? parameters will break if you change to a direct connection.