Doug Robbins Mail Merge Tool Kit- ERROR MESSAGE 13 Type Mismatch

Question

Hello,

I have done the same process for a couple of weeks now and never had this message before. "13 Type Mismatch" Error comes up and doesn't send to my drafts folder- not completing the mail merge.

I have checked the data, there are no blank rows, no @'s missing or additional semicolons, no excel errors- i have no clue what's stopping me from completing this mail merge

Please help :)

Answer 1

|| | -------- | A Run Time Error 13 – Type mismatch will occur if:

 

|| | -------- | 1.       There is only one field in the data source;

2.       There are no mergefields in the main document;

3.       The data in the field that contains the path\file names for attachments contains characters that cannot be used in a filename such as an apostrophe;

4.       The incorrect path separators have been used in the data in the field that contains the path\file names for attachments.

5.       There are empty columns or empty rows before the start of the data in the data source.

6.       The result of a calculation in an Excel data source returns one of the following errors: #DIV/0!,  #NAME?, #N/A, #NUM, #VALUE!, #REF!, #NULL, #SPILL!, #CALC! The type mismatch error will occur whether or not the field (column) containing that error is used in the mail merge main document.

 

If you cannot sort it out, send me a copy of the mail merge main document and the data source and I will investigate the issue.

A Run Time Error 13 – Type mismatch will occur if:

 1.       There is only one field in the data source;

2.       There are no mergefields in the main document;

3.       The data in the field that contains the path\file names for attachments contains characters that cannot be used in a filename such as an apostrophe;

4.       The incorrect path separators have been used in the data in the field that contains the path\file names for attachments.

5.       There are empty columns or empty rows before the start of the data in the data source.

6.       The result of a calculation in an Excel data source returns one of the following errors: #DIV/0!,  #NAME?, #N/A, #NUM, #VALUE!, #REF!, #NULL, #SPILL!, #CALC! The type mismatch error will occur whether or not the field (column) containing that error is used in the mail merge main document.

If you cannot sort it out, send me a copy of the mail merge main document and the data source and I will investigate the issue.

Answer 2

The error message "Run-time error '13' Type mismatch" in a mail merge scenario is a known bug when using Automation with certain Office components on 64-bit systems.

In similar cases, Microsoft has confirmed this as a product bug and provided a hotfix/update for the affected component. The documented resolution involves updating/replacing the relevant handler component (for example, in Dynamics NAV scenarios) with a fixed version of the DLL and re-registering it.

For this Word mail merge toolkit scenario, the practical steps are:

1. Ensure Office/Word and Windows are fully updated via Microsoft 365 Apps updates and Windows Update.
2. If the issue started recently after previously working, check whether any recent Office or Windows updates were installed around the time the error began; if so, installing the latest cumulative updates may include a fix.
3. If the mail merge toolkit relies on external automation components (COM add-ins, DLLs), verify that they are compatible with the current Office bitness (32-bit vs 64-bit) and Windows version. A type mismatch often occurs when 32-bit automation code is used against 64-bit Office, or vice versa.
4. If the toolkit vendor (Doug Robbins) provides an updated version or patch for current Office builds, install that update so that the automation code matches the current environment.

If the environment involves a specific Microsoft component similar to the Dynamics NAV Application Handler, the documented pattern is to:

• Obtain the relevant hotfix/update package from Microsoft.
• Replace the affected DLL with the updated version in its installation folder.
• Re-register the DLL using regsvr32 from an elevated command prompt.

Because this is a confirmed type-mismatch bug in automation rather than a data issue, focusing on updating/fixing the automation components and ensuring bitness compatibility is the key path to resolution, rather than further cleaning the Excel data source.

---

References:

• "Run-time error '13' Type mismatch" error message when you use Automation to send email messages by using Microsoft Office 2010 in Microsoft Dynamics NAV 2009 on a 64-bit Operating System
• "Type Mismatch" error message when you run a VBA macro in a 64-bit version of an Office 2010 application