Ready to get started?

Learn more about the CData ODBC Driver for MailChimp or download a free trial:

Download Now

Update MailChimp Data with a Microsoft Access Linked Table

Update MailChimp data by creating a linked table in Microsoft Access with the CData MailChimp ODBC Driver.

CData ODBC drivers connect your data to any database management tool that supports Open Database Connectivity (ODBC). This includes many of the most popular productivity tools, adding new capabilities for document sharing and collaboration. Using the CData ODBC driver for MailChimp, you can update live MailChimp data in Microsoft Access; for example, you can make updates that can be immediately seen by other users.

Connect to MailChimp as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

You can set the APIKey to the key you generate in your account settings, or, instead of providing your APIKey, you can use the OAuth standard to authenticate the application. OAuth can be used to enable other users to access their own data. To authenticate using OAuth, you will need to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL by registering an app with MailChimp.

See the "Getting Started" chapter in the help documentation for a guide to using OAuth.

Create a Linked Table to Lists Data

Follow the steps below to create a linked table, which enables you to access live Lists data.

  1. On the External Data tab in Access, click ODBC Database.
  2. Select the option to link to the data source. A linked table will enable you to read from and write data to the Lists table.
  3. Select the CData MailChimp data source from the Machine Data Source tab.

  4. Select the Lists table. For more information on this table, see the "Data Model" chapter in the help documentation.
  5. Double-click the linked table to make edits. The linked table will always have up-to-date data and any changes will be reflected back to the underlying table.