How can I get this 8 year old VBA 64-bit compiler bug fixed?

📝 Title: How to Fix the 8-Year-Old VBA 64-Bit Compiler Bug in Microsoft Office

👋 Hey there, fellow VBA enthusiasts! 🚀 Today, I want to address a long-standing issue that has been bugging many developers like us for years: the infamous 8-year-old VBA 64-bit compiler bug in Microsoft Office. 😱💥 Don't worry, though! I've got some easy solutions that can help you fix this issue. So, let's dive right in and solve this bug together! 💪🔧

Understanding the Bug 🐛

The bug manifests itself when using a 64-bit VBA host, such as Access 365 or Excel 2016, and creating a class module with a Class_Terminate() sub. The problem arises when evaluating conditions inside an IF statement or a WHILE loop. The incorrect evaluation causes unexpected behavior and incorrect results. 😫

Reproducing the Bug 🔄

To see the bug in action, follow these steps:

1. Create a class module named SomeClass with the following code:

   Private Sub Class_Terminate() End Sub

2. Create a module named Test with the following code:

   Function ReturnFalse(o As Object) As Boolean ReturnFalse = False End Function Sub Test() Debug.Print ReturnFalse(New SomeClass) If ReturnFalse(New SomeClass) Then Debug.Print True Else Debug.Print False End If End Sub

When running the Test subroutine, you'll notice that in a 32-bit VBA host, the expected output is:

False
False

But in a 64-bit VBA host, it outputs:

False
True

The Call to Action 🔔💬

Now that you've experienced the bug firsthand, it's time to take action! Here are some steps you can follow to help get this bug fixed:

1. Report the Bug: Visit the Microsoft Office support forum or use the Smile button in Excel to report the bug directly to Microsoft. Here are some helpful links that can guide you:

   • How to Report VBA Bugs

   • Excel Feedback & Uservoice

2. Engage with the Community: Join discussions on platforms like Stack Overflow or uservoice.com. Upvote and contribute to existing posts that discuss the bug. Here are some active threads to get you started:

   • VBA takes wrong branch at If-statement - severe compiler bug?

   • Fix inlined member calls on user objects on 64-bit VBA

3. Spread the Word: Share this blog post on social media, forums, or with fellow VBA enthusiasts to raise awareness about the bug. The more attention it gets, the higher the chances of getting it fixed.

🚨 Let's come together as a community and make a difference by ensuring that this long-standing bug gets the attention it deserves! Together, we can help Microsoft address and fix this issue, empowering developers worldwide. 🌍💪

✨ Keep coding, stay curious, and never stop exploring new possibilities with VBA! 😄👩‍💻👨‍💻