Yes, using the RefreshLink method doesn't check for driver changes in the DSN. The DSN connection details once used must be cached somewhere against each table (in particular the driver used). It's similar to the way the username and password credentials are stored somewhere when connecting, yet...
I thought I should stop lurking and actually contribute. Thanks for that summary (sonic8) which was the first confirmation I could find that helped me isolate the issue and resolve it by rolling back to build 2204.
Just to muddy the waters a little, I have two points to add.
1) This issue hit...