Background

Total Access Emailer is a Microsoft Access program that lets you send personalized emails with attachments from your tables and reports to everyone on your list.

The Standard Version is an Access add-in that works directly with your currently opened database.

The Professional Version includes the Standard Version plus a programmatic interface that lets you automate email blasts from VBA. This lets you run email blasts from a button or event and avoids requiring users to run the add-in and prevents them from modifying your settings. The Professional Version includes a royalty-free runtime license so you can distribute your Access databases with Total Access Emailer features to people who don't own it.

Problem

An email blast that works from the add-in, doesn't work properly when sent from the VBA programmatic interface.

Solution

Troubleshooting Email Blasts from the VBA Interface

There may be several causes for an email blast to fail from the VBA interface. It may be a global problem that affects all email blasts or something specific to the email blast. Here are some steps to diagnose the problem.

Does the email blast run properly from the add-in?

The Total Access Emailer add-in has a user interface that offers much more feedback than the VBA interface if there are problems. It's critical to make sure the email blast first works from the add-in because the VBA approach sends the same email blast. Some things to check:

1. Running it from the Access version that you and your users run. You need to have the right version of Total Access Emailer to work with your Access version. If so, the VBA libraries that come with it also work with that Access version and earlier ones.
2. From Options, make sure the SMTP settings are correct. If they are not, none of the email blasts work.
   • If you're using Office 365 and are having trouble with configuring it, visit SMTP Relay Configuration to Send Emails from Total Access Emailer with Office365 
3. Preview the email blast. Send the email blast to your own email address to make sure it's working.

Once we confirm the email blast works from the add-in, we can review the VBA Interface.

VBA Interface Issues

Information on setting up the VBA programmatic interface is available at Sending Microsoft Access Email Blasts Programmatically (VBA). Make sure the steps are followed.

For instance, if the Library Reference is missing or incorrect, it generates this compile error:

Sub or Function not defined

Here are some issues to consider:

1. Verify the data source for the email blast can be opened from the Access database without errors

2. Choose the right library file to reference. Total Access Emailer has three library files depending on whether your database is an ACCDB or MDB, and if you're running the 32 or 64-bit version of Access.

   • See Adding the Total Access Emailer Library Reference to Email from Microsoft Access Modules for details.

   • If you converted a MDB database to an ACCDB and your MDB was referencing the library for MDBs (TAEmailR.mde), make sure you change the reference to the ACCDB version.

   • Verify the referenced library is current. If you upgraded Total Access Emailer, make sure you're not referencing a library from an earlier version.

   • If you didn't upgrade Total Access Emailer, the referenced library may not work with newer versions of Access. Current shipping versions of Total Access Emailer Professional (2010 and later) include libraries that work for users running Access 2003, 2007, 2010, 2013, and 2016. This includes 32 and 64-bit versions of Access 2010 and later.

3. The sample database in the Professional Version of Total Access Emailer is already configured to use the VBA runtime library to send email blast. Verify that works. Start with the add-in if you haven't already done that to verify the SMTP settings.

4. Create a simple email blast and/or verify another email blast from your database to see it it works from the VBA interface. This helps to isolate whether it's email blast specific or not.

If other email blasts work (especially if they use the same data source), but this particular one doesn’t, contact us with a report for the email blast and/or a copy of the database so we may investigate further.

If you've discovered other causes not in our list, please let us know so we may share it with everyone. Thanks for your help.

Additional Support Resources

• Support Options
• Product Information
• FAQs
• Updates
• User Manual
• PDF Fact Sheet