

This basically explains to me why the issue only occurs about every half a year, but not really, why this causes application crashes with Excel 64-bit, but not with Excel 32-bit. I reasearched more about this "cleanup-process" the Add-In is doing and I found anĪbout VB behaviour of compiling and decompiling code. KB smaller than before and we were able to open them again without any crashes or error messages.

After we applied this script (which is listed at the bottom of the page), the three test files were all about 70 Half a year later, they will be guaranteedĪnother crash, which can be solved by recompiling the project again.Īdd-in, which shall clean-up the macro cache of a file.

So, as the title says, at my work, we have a customer, which works a lot with Excel and macros.

I don't know if I'm correct here but I'm dealing with a really strange issue regarding Excel and VBA and a friend of mine recommended this forum to post the question.
