Problems compiling Word vba -addin in 64-bit office newer than version 2507

Question

We have an Word-vba addin that has worked both in 32-bit and 64-bit Office. Now (after Word version 2508) if you compile it in 64-bit word (2508 or later), it does not work in Word that is version earlier than 2508.

There comes no error message, Word just does not start at all.

• Compile in 32-bit Word (no matter what version) -> Works in whatever version 32-bit or 64-bit
• Compile in 64-bit Word version 2507 or earlier -> Works in whatever version 32-bit or 64-bit
• Compile in 64-bit Word version 2508 or later -> Works in Word version 2508 or later but does not work in Word version 64-bit 2507 or earlier.
• We do not have 32-bit version that is earlier than 2510, but I guess that it works in all 32-bit versions.

There has to be something wrong in 64-bit compiler. Or could you give some tips what should be done?

Answer 1

What happens if you place a copy of the 2508 or later compiled .dotm file in the Templates folder of a 2507 or earlier machine and then use File>Open to open the .dotm file.

Answer 2

It seems that you are encountering compatibility issues with your Word VBA add-in when compiling in 64-bit Office versions 2508 and later. This is likely due to changes in the VBA compiler or the architecture differences between the versions. Here are some points to consider:

1. Compatibility with 64-bit Office: When you compile your add-in in 64-bit Office version 2508 or later, it may introduce changes that are not backward compatible with earlier versions of Office. This can lead to issues where the add-in fails to load without any error messages.
2. Using 64-bit Safe Declare Statements: Ensure that your code uses 64-bit safe declare statements and the PtrSafe attribute. This is crucial for compatibility across different versions of Office. If your code does not include these, it may not function correctly in older versions.
3. Testing in Different Versions: Since you have noted that compiling in 32-bit Word works across all versions, it may be beneficial to continue using the 32-bit version for broader compatibility, especially if your users are on various Office versions.
4. Error Handling: While you mentioned that there are no error messages, consider adding error handling in your VBA code to capture any issues that may arise during execution. This might help identify specific problems when running in older versions.
5. Contacting Microsoft Support: If the issue persists, it might be worthwhile to reach out to Microsoft support or check their documentation for any known issues related to the 64-bit compiler in Office versions 2508 and later.

In summary, ensure that your code is compliant with the latest standards for 64-bit Office and consider maintaining compatibility by compiling in 32-bit if necessary.

---

References:

• Compatibility between the 32-bit and 64-bit versions of Office
• Compile error in hidden module: <module name>

Answer 3

Dear Ensi Testaaja

Thank you for posting in the Microsoft Community. We are happy to help you.

According to its description, it looks like that the issue you’re experiencing is related to VBA behavior and compatibility across different Word versions.

If my understanding is correct, as our category focuses on Office 365 products, the concern you have is more related to VBA. To ensure that you get professional help and avoid incorrect information from our side, we suggest you post on the Stack Overflow for expert assistance. This is a specific channel related to VBA.

As a moderator, I have limited resources and concerns about VBA that go beyond the support available in this community. In Stack Overflow community, you'll get the most qualified group of respondents, and other partners who read the forums regularly can share their knowledge or learn from your interaction.

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link

Sorry for directing you to a different community. The members of the category you posted in focus on Microsoft 365 users, so to get quicker and better help, I redirected you to the right place.

I appreciate your patience and understanding and thank you for your time and cooperation.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.