Odd behaviour when using a macro enabled template

[MrBaseline]

Hi,

I have a macro enabled template that has been evolving over several years. Lately, it shows some really odd behaviors:

1. When I double-click it to spawn an instance of the template, the macro execution is really slow. It is not isolated to any specific code snippet, it is a general thing. Once I save it, close Excel, and open the saved file, it executes at the excepted speed. Every time. I've also dug up old versions of the same macro template that has not preciously shown this behavior; they are now showing the same symptom.

2. The other really odd thing is that when I close the newly created instance, the dialog box to enter the password to access VBA-macros is somtimes (not always) displayed. This behavior also goes away once I save the instance and reopens it.

I can come to no other conclusion than that there is something going on in my computer that somehow interferes with Excel (at least to cause [1]. [2] is just weird).

I'm not really expecting anyone to know the exact cause, but if anyone has had similar mysteries and resolved them, pointers to strategies to do so would be appreciated.

Thanks!

[Leith Ross]

Hello MrBaseline,

Just a guess, but you probably updated to a newer version of Office. Your profile shows you are running 2013. 2013 has more than it's share of weird behaviours. One of which is the VBA password dialog displaying when you close a macro enabled workbook. I don't know if there is fix or workaround available for this problem. Another common problem is slow execution and file bloat. Both of these problems have to due with the design of the 2013 environment and not Excel nor VBA.

[MrBaseline]

Hello MrBaseline,

Just a guess, but you probably updated to a newer version of Office. Your profile shows you are running 2013. 2013 has more than it's share of weird behaviours. One of which is the VBA password dialog displaying when you close a macro enabled workbook. I don't know if there is fix or workaround available for this problem. Another common problem is slow execution and file bloat. Both of these problems have to due with the design of the 2013 environment and not Excel nor VBA.

Thanks! Well, don't really know about updates, since they magically are being conducted from my company's network. Quite plausible though. Also good to know about the known issue with the password box.

Just have to wait for the next silent update then I guess...