. Advertisement .
..3..
. Advertisement .
..4..
Here is a code for the programs, and for some strange reason, I got the warning text:
A problem was encountered while trying to log into or create the
production database. Details: [Microsoft][ODBC Driver Manager] Data
source name not found and no default driver specifiedeven though I copied some suggestion codes, It does not work. What can I do about the “ data source name not found and no default driver specified ” issue? Is there a better approach?
The cause: This error happens because you had the Data Source Name in User DSN, but it should be in System DSN.
Solution: You have to change the Data Source Name from User DSN to System DSN as the description below:
Referring to the error: [Microsoft][ODBC driver Manager] Data source name and default driver not found.
This error indicates that the Data Source Name (DSN), which you specify in your connection configuration, is not being recognized in the Windows registry.
It is essential that your ODBC driver’s executable-linking format (ELF), matches your application. You will need a 32-bit driver to run a 32 bit application and a 64bit driver to run a 64 bit application.
These can be configured to match 32-bit drivers. However, 64-bit applications will not find the DSN because the registry has DSN information at different locations depending on ELF (32-bit or 64-bit).
Make sure that you’re using the correct ODBC administrator tool. The default ODBC Administrator tool for 32-bit and 64 bit Windows is
c:\Windows\System32\odbcad32.exe. The default 64-bit version is used on 64-bit Windows machines. You will need to runC:\Windows\SysWOW64\odbcad32.exeif you want to use 32-bit ODBC Administrator on a 64 bit Windows system.This is where I see people getting confused. A user who uses the 64-bit ODBC Administrator default to set up a DSN, thinking it’s for a 32 bit DSN, is using this 64-bit ODBC Administrator. When the 32-bit application attempts connect with that DSN, it returns “Data source not found …””.
Also, ensure that the DSN spelling matches the DSN configured in the ODBC administrator. A DSN can be misaligned by one letter.
Although it may not be the exact same brand, it is a common problem when using ODBC data sources names.
Referring to your OLE DB provider portion of your question it seems to be a similar problem. The application cannot locate the configuration for the specific provider.