Hello, I’m running EE3 for our registration process on our site: http://www.nanoosebaycamp.ca I’m wondering if there is a way to link Microsoft Access to the attendee database so I can run custom reports on my attendees and make modifications to their information.
If you might happen to know of a better way other than Access, I would greatly appreciate the feedback. Thanks very much, I look forward to hearing back.
The attendee information is kept in tables in the MySQL database that is set up for your WordPress installation. There is a way to use Microsoft Access as a frontend to access those tables (https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-examples-tools-with-access-linked-tables.html but it’s not something that I have any experience actually setting up. Also be aware that the data for a particular attendee may be spread over several tables. For example, a row in the wp_events_attendees table will hold the attendee id, first name, last name, etc. That attendee id will then correspond to several rows in the wp_events_answer table that hold the answers to questions in the registration form.
Hi Sidney, do you know if there is a way (custom script or other) that I can get EE to put all the information from one registration into one MySQL table? I’m fine if EE keeps data across multiple tables for EE purposes, but I’m thinking it’s going to be easier for me if I can get all the data into one table for Access as I don’t have an extensive background working the MySQL.
Event Espresso doesn’t have a function that puts all attendee details into one table, but most of the attendee details (including name and email) are in the _events_answer table.
You might also consider using MySQL Workbench as an alternative to Access.
The support post ‘EE3 and Microsoft Access Integration’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
Support forum for Event Espresso 3 and Event Espresso 4.