ODBC driver loss Solution

ODBC driver loss Solution

When I run SqlDbx to connect to the database today, an error is reported, prompting that the corresponding ODBC driver is not found. Open the ODBC Management Panel and check that the driver is missing.
This is the case after a cost computing software is uninstalled today. For online search, only odbcconf.exe can be used to re-register the ODBC Driver.
Registration Method:
There are several script files in the % systemroot % \ System32 directory to complete driver registration:
Odbcconf.exe/S/Lv odbcconf. log/F % systemroot % \ system32 \ odbcconf. rsp
Odbcconf.exe/S/Lv odbcconf. log/F % systemroot % \ system32 \ mdaccore. rsp
Odbcconf.exe/S/Lv odbcconf. log/F % systemroot % \ system32 \ sqlclnt. rsp
Odbcconf.exe/S/Lv odbcconf. log/F % systemroot % \ system32 \ redist. rsp

However, after registration, you will find that the SQL Server Native Client, MySQL Connector/ODBC drivers that existed before uninstallation are absent, so you will never reinstall them.
Later I opened rsp and saw the text content. I thought I could just create a new driver to register the two drivers.
Use NotePad to create a file other. rsp and save the following content

INSTALLDRIVER "MySQL ODBC 5.3.6 Unicode Driver|Driver=myodbc5w.dll|Setup=myodbc5s.dll|"INSTALLDRIVER "MySQL ODBC 5.3.6 ANSI Driver|Driver=myodbc5a.dll|Setup=myodbc5s.dll|"INSTALLDRIVER "SQL Server Native Client 10.0|Driver=sqlncli10.dll||"

Then run odbcconf.exe/S/Lv odbcconf. log/F % systemroot % \ system32 \ other. after rsp registration, open the ODBC Management Panel and check that the two drivers are back. Create a DSN and test everything!

I hope it will be helpful to you.