his is an interesting bug!!
Yes, I can reproduce the bug easily. Unfortunately, I can still repro this
issue with the latest ACE driver released with Office 2010.
I can only say that the only workaround is not to use the same name for both
user DSN and system DSN.
Thanks for reporting this bug to us. I will contact the appropriate team to
see whether this issue can be addressed.
btw, DSN is a recommended method to deploy the application, compared to
connection string. This is because the application do not need to use a
hard-coded connection string. In deployment environment, the ability of
changing the underlying data source (say, Access file) may usually be needed.
WDAC Team, Microsoft.
P.S. This newsgroup will be out-of-support very soon. We recommend customers
to use the forum to ask ODBC questions in the
future, where you can find more experts (Forum is at:
"Mary Chipman [MSFT]" wrote: