Wow...this bug is a PITA. While I wait for MS to send out a fix, people have suggested the ODBC Driver 17 for SQL Server is unaffected to this problem. What is the difference between using the ODBC Driver 17 for SQL Server and SQL Server native Client 11.0 driver? I have always used the SQL...