This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 19%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVD%3C/text%3E%3C/svg%3E)
Hello,
I am hoping someone could provide me with some insight to as to what drive/install/dictate the following registry value.
We have been having issue with a few users who were unable to open a custom excel spreadsheet an run a custom script. The following message typically pops up when they try to run the macro "Run-Time Error '-2147467259 (80004005): [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.
The solution, was to import that SQL Server registry value from a working machine into workstation with this issue and it appear to have resolve the problem.
Therefore, I hope someone could point me in the right direction as to what set those values? Is it out of the box windows installation? or by a different Microsoft product such as SQL.
This key is from ODBC Driver : Driver Specification Subkeys
Download ODBC Driver for SQL Server
I have tired downloading and installing it and on the problem machine that value still remain empty afterward.
Have you installed the 32-bit version ?
The installer does not work for me.
But you said you installed it : "I have tired downloading and installing it..."
What "does not work" mean ?
Is there any error returned ?
The Wow6432Node branch is for 32-bit applications on 64-bit OS
So it should be filled by the 32-bit installer...
The driver "SQL Server" comes with the OS, but this is a very old driver that lacks support for several features in modern versions of SQL Server
You would be somewhat better off using SQL Server Native Client 11.0, which you also seem to have.
Even better may be to download and install the ODBC 17 SQL Server driver, which is the most recent.
For whatever, reason we have remove and reinstalled both the SQL Server Native Client for 10 and 11 and from my testing it did not appear to be driven from that. However, like you said it might have came with the OS.