Share via

2.1.13 Microsoft Access

  • Article

Microsoft Access is a desktop database application that helps users track and report data, and share data more securely by using the Web. For common operations such as authenticating users, accessing data and files, and managing database files and data, Microsoft Access 2013, Microsoft Access 2010 and Microsoft Office Access 2007 use the protocols that are identified and described in section 2.2.1. To support application-specific operations, Access 2013, Access 2010 and Office Access 2007 use additional protocols.

To access external data sources, Access 2013, Access 2010 and Office Access 2007 use the data access protocols that are described in section 2.2.1.4 in addition to OLE DB, as described in [MSDN-OLEDB], and Open Database Connectivity (ODBC), as described in [MSDN-OpenDBConnectivity]. ODBC provides client-side APIs for accessing data by using ODBC drivers, and these APIs use the Tabular Data Stream Protocol, as described in [MS-TDS], to communicate with Microsoft SQL Server.

To add, modify, and synchronize data between an Access database and a SharePoint list (1), Access 2013, Access 2010 and Office Access 2007 use the Lists Web Services Protocol, as described in [MS-LISTSWS]. Access 2013, Access 2010 and Office Access 2007 also use the Lists Web Services Protocol to create lists (1) from tables in existing Access 2013, Access 2010 or Office Access 2007 databases. After a list (1) is created from an existing table, Access 2013, Access 2010 and Office Access 2007 use the Views Web Service Protocol, as described in [MS-VIEWSS], to modify the default view of the list (1) by hiding and displaying specific columns.

Access 2013, Access 2010 and Office Access 2007 also use the Web Part Pages Web Service Protocol, as described in [MS-WPPS], to provide a feature that enables users to open a list (1) as an Access database and display a specific form, instead of opening the list (1) in a Web browser.

For a complete list of the protocols that are used for application-specific operations, see section 2.2.5.