Differences between ODBC drivers and built-in drivers for external data
In Microsoft Access, you can import, export, or link data from a number of different database, spreadsheet, and text file formats. To do this, Access uses either a built-in driver or an ODBC driver.
Built-in drivers
Access contains built-in drivers that enable you to import, export, or link the following types of data: other Microsoft Access databases, Microsoft Access projects, Paradox, dBASE, Microsoft Excel, Microsoft Exchange, HTML, Lotus 1-2-3 spreadsheets, Microsoft Outlook, Microsoft Windows SharePoint Services, fixed-width text files, delimited text files, and XML.
If a built-in driver for a type of data has been installed, that type will be available in the Export, Import or Link dialog boxes. All built-in drivers are installed automatically when you install Access. ODBC drivers may also be installed on your computer for the products listed above, but Microsoft recommends you use a corresponding built-in driver when available.
ODBC drivers
You can use ODBC drivers to connect to Microsoft SQL Server databases, Microsoft FoxPro databases, and data from other programs that provide 32-bit drivers in compliance with ODBC Level 1 to access their data files. Microsoft Access automatically installs the Microsoft SQL Server ODBC driver (Sqlsrv32.dll), the Microsoft FoxPro ODBC driver (vfpodbc.dll), the Oracle ODBC driver (msorcl32.dll), and some ODBC support files (Help files and the Control Panel/Administrative Tools Data Sources (ODBC) icon).
Third-party vendors may supply additional ODBC drivers and documentation that support other data formats. For more information about whether an ODBC driver is available for a particular type of data, contact the vendor of the program that produces that type of data. Access requires 32-bit ODBC drivers that are in compliance with ODBC Level 1.
Other Microsoft products and products from other vendors may also contain ODBC drivers. If you want to know whether these ODBC drivers have been tested and verified for use with Access, contact the driver vendor.