Records purchased online contain 3 years of driver license history. When CDL Employer Information is selected, records contain a complete driver license history, which may be more than 3 years. If you need a record with the original issue date or more than 3 years of history complete the paper form and submit it to ITD. 64-bit ODBC drivers for Access (Office 2016) I’m running 64-bit Windows 7 Pro SP1. I needed the 64-bit odbc drivers for Access databases and naturally thought that these would be installed if I upgraded from 32-bit Office 2010 to 64-bit Office 2016.
ODBC is an API that uses Structured Query Language (SQL) as the database access language. You can access a wide variety of database management systems (DBMSs) with the same ODBC source code that is directly incorporated into an application's source code. With the Microsoft ODBC Desktop Database Drivers, a user of an ODBC-enabled application can open, query, and update a desktop database through the ODBC interface.
The Microsoft ODBC Desktop Database Drivers are a Microsoft Jet-based set of ODBC drivers. Whereas Microsoft ODBC Desktop Database Drivers 2.0 include both 16-bit and 32-bit drivers, versions 3.0 and later include only 32-bit drivers that work on Windows 95 or later, Windows NT Workstation or Server version 4.0, Windows 2000 Professional, or Windows 2000 Server. These drivers provide access to the following types of data sources:
Microsoft Access
Microsoft Excel
Paradox
dBASE
Text
See Visual FoxPro ODBC Driver for detailed documentation about the Microsoft Visual FoxPro® ODBC Driver.
Note
Access Driver 2019
Update firmware with any supported mobile device! Android, Android Logo, iOS, iPhone, iPad, Apple, Apple Logo and all other product names and services are not affiliated with Axxess. ThinkVantage Access Connections 6.26.88 on 32-bit and 64-bit PCs. This download is licensed as freeware for the Windows (32-bit and 64-bit) operating system on a laptop or desktop PC from drivers without restrictions. ThinkVantage Access Connections 6.26.88 is available to all software users as a free download for Windows.
Access to other data sources, such as Lotus 1-2-3, Microsoft Exchange, and HTML, is enabled by installable ISAM (IISAM) drivers. For more information about these drivers, see 'Accessing External Data' in the Microsoft Jet Database Engine Programmer's Reference. ODBC Desktop Database Drivers 4.0 do not support Btrieve and EMS data formats.
This section contains the following topics.
Build connection strings and enumerate installed ODBC drivers (32bit and 64bit)
Before we can build the connection string we need to ensure that the ODBC drivers are available on our system.
ODBC Drivers
The standard ODBC drivers for MS Access 97 (*.mdb) and MS Excel 97 (*.xls) should be available on all Windows installations:
Microsoft Access Driver (*.mdb)
Microsoft Excel Driver (*.xls)
... but the MS Office 2010 ODBC drivers for *.xlsx and *.accdb might not be installed on your system.
This means it might be required to install the drivers first, if you want to use an Excel file with the extension .xlsx or an Access file with the extension .accdb.
Access Driver Download
Microsoft Access Driver (*.mdb, *.accdb)
Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)
Install ODBC Driver for *.accdb and *.xlsx
You can download the latest version of 'Microsoft Access Database Engine (2010)' (for MS Access and MS Excel) here:
http://www.microsoft.com/en-us/download/details.aspx?id=13255
Important: There are different drivers for 32bit and 64bit applications. If you want to build a 32bit application, then you need to install the 32bit version of the driver, because a 32bit application cannot use the 64bit driver and a 64bit application cannot use the 32bit driver!
ODBC Connection String
The connection string for MS Access and MS Excel has the following syntax:
Driver={DRIVER};Dbq=FILEPATH;
We need only 2 parameter: the ODBC driver and the file path.
e.g.
Driver={Microsoft Access Driver (*.mdb)};Dbq=C:tempsomedatabase.mdb;
Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};Dbq=C:tempsomesheet.xlsx;
The 'driver' can be different depending on the language, so it could be required to enumerate the installed drivers and search for the file extension.
e.g. 'Microsoft Excel Driver' is called 'Microsoft Excel Treiber' in German.
Enumerate ODBC Drivers
The system stores a list of the installed ODBC drivers in the registry HKEY_LOCAL_MACHINE.
There are two different locations for 32bit and 64bit drivers:
32bit: HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INIODBC Drivers
64bit: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBCINST.INIODBC Drivers
Sample code to enumerate 32bit ODBC drivers:
using Microsoft.Win32;
using (RegistryKey reghklm = Registry.LocalMachine)
using (RegistryKey regdrivers = reghklm.OpenSubKey(@'SOFTWAREODBCODBCINST.INIODBC Drivers'))
{
if (regdrivers != null)
{
foreach (string driver in regdrivers.GetValueNames())
{
// display drivers
MessageBox.Show (driver);
}
}
}
Check if ODBC Driver is installed
We can build a small function to check if a specific ODBC driver (language) is available, e.g. 'Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)'
using Microsoft.Win32;
private bool IsODBCDriverInstalled(string searchfor)
{
using (RegistryKey reghklm = Registry.LocalMachine)
using (RegistryKey regdrivers = reghklm.OpenSubKey(@'SOFTWAREODBCODBCINST.INIODBC Drivers'))
{
if (regdrivers != null)
{
foreach (string driver in regdrivers.GetValueNames())
{
if (driver.IndexOf(searchfor) != -1) return true;
}
}
}
return false;
}
...
// check if English(!) Excel (2010) driver is installed
string driver= 'Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)';
if (IsODBCDriverInstalled(driver))
{
// driver installed
}
else
{
// driver not found
}
The function returns false if e.g. the German version is installed, so it might be better to enumerate the drivers and search for the file extension '*.xlsx'.
Find Access or Excel ODBC Driver for File Extension
We just need to modify the code a bit, so that the function returns a valid driver (any language) for the given file extension.
The function returns an empty string if no valid driver was found.
using Microsoft.Win32;
private string GetODBCDriverForExtension(string extension)
{
using (RegistryKey reghklm = Registry.LocalMachine)
using (RegistryKey regdrivers = reghklm.OpenSubKey(@'SOFTWAREODBCODBCINST.INIODBC Drivers'))
{
if (regdrivers != null)
{
foreach (string driver in regdrivers.GetValueNames())
{
if (driver.IndexOf(extension) != -1) return driver;
}
}
}
return ';
}
...
// search for .xlsx (MS Excel 2010) driver
string xlsxdriver = GetODBCDriverForExtension('*.xlsx');
// search for .accdb (MS Access 2010) driver
string accdbdriver = GetODBCDriverForExtension('*.accdb');
If you prefer e.g. the English driver: check if the English driver is installed - otherwise use any valid driver for the file extension.