Modules & VBA:: Automatically Linking Database With ODBC Connection Jun 26, 2015. Hi all, I am using access as a FE for a mysql BE. I have the odbc mysql driver installed on the workstations. My issue is that I don't want the users to be able to use the driver in say excel. If you were setting up an ODBC call manually on the second to last page it has check boxes for Use ANSI quoted identifiers. = QuotedId Use ANSI nulls, paddings and warnings. = AnsiNPW and on the last page it has a check box for Perform translation for character data. = AutoTranslate On our home grown databases and many of our.
-->Your computer may contain a variety of ODBC drivers, from Microsoft and from other companies. This topic describes how to use the Windows ODBC Data Source Administrator to check the version of the installed ODBC drivers.
To check the ODBC SQL Server driver version (32-bit ODBC)
- In the ODBC Data Source Administrator, click the Drivers tab.Information for the Microsoft SQL Server entry is displayed in the Version column.
Note
For connections to Azure Active Directory Authentication for SQL Database install the latest driver, such as ODBC Driver 13.1 for SQL Server.
![Vba Check If Odbc Driver Installed Automatically Vba Check If Odbc Driver Installed Automatically](https://3ot7w31w8uv4uacjf3wz7yj9-wpengine.netdna-ssl.com/wp-content/uploads/2016/12/2016-12-12_08-43-47.png)
See Also
![Powershell get odbc driver version Powershell get odbc driver version](https://dev.mysql.com/doc/connector-odbc/en/images/myodbc-win-odbcadmin-driverselect-5.3.png)
Symptoms
When you try to create an ODBC DSN for drivers that are provided by Microsoft Access in the Data Sources ODBC Administrator, the attempt fails. This problem occurs if you're using a Click-to-Run (C2R) installation of Office. Depending on the version of Office, you may encounter any of the following issues when you try this operation:
- The ODBC drivers provided by ACEODBC.DLL are not listed in the Select a driver dialog box.
- You receive a 'The operating system is not presently configured to run this application' error message.
- You receive an 'Unable to load odbcji32.dll' error message.
- You receive a 'The driver of this User DSN does not exist. It can only be removed' error message together with the platform showing N/A.
Affected drivers:
- Microsoft Access Driver (*.mdb, *.accdb)
- Microsoft Access Text Driver (*.txt, *.csv)
- Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)
- Microsoft Access
- Microsoft Excel
Additionally, if you try to define an OLEDB connection from an external application (one that's running outside of Office) by using the Microsoft.ACE.OLEDB.12.0 OLEDB provider, you encounter a 'Provider cannot be found' error when you try to connect to the provider.
Cause
Click-to-Run installations of Office run in an isolated virtual environment on the local operating system. Some applications outside Office may not be aware of where to look for the installation in the isolated environment.
Resolution
ODBC connections to be used in Office applications
You can work around the issue by creating a DSN from within an Office application, such as Access, instead of using the ODBC Administrator. To create a new DSN in Access, follow these steps:
- On the ribbon, select External Data > ODBC Database.
- Select Import or Link, and then click OK.
- Select the tab for the kind of DSN that you want to create (File Data Source or Machine Data Source), and then click New.
- Select the appropriate driver along with any required information to complete the entry.
- After the DSN is created, click Cancel to exit the remaining Import/Link steps.
- The DSN should now appear in the ODBC Administrator, and you can use it in any Office application.
ODBC or Microsoft.ACE.OLEDB.12.0 OLEDB provider connections that will be used outside of Office
You must install an MSI installation of the Microsoft Access Database Engine from one of the following sources so that the calling application can locate the driver and provider.
Note If Office 365 is already installed, side-by-side detection will prevent the installation from proceeding. To install the package, perform a quiet installation by running a command such as the following:
<File location>:<File name> /quiet
For example: C:AccessDatabaseEngine.exe /quiet