HELP!!! "Code execution has been interrupted"

[x-amount]

But I havent pressed anything!!!

There is definite problem, as the "Code execution has been interrupted" error message appears seemingly at random (although if the workbook doesnt change it is the same points), and for no reason.

If I click the continue button the macro runs exactly as planned, but still there seems to be no rhyme or reason as to why this happens!?

It even invokes on the workboon_open function.

Any ideas???

 

[biddingers]

SOLUTION to this issue. (and other issues as well)

I would describe the workbook I am using as very complex and is about 20mb in size. I use windows xp SP2 with Office 2003 SP3 on my main computer.

I make changes to either data or macro's in this workbook almost daily and with each save of the workbook it increases in size.

I run the same setup on my laptop except there have been no service packs installed for Office.

Every once in a while I will save the workbook on the laptop and the save will reduce the size of the workbook by 2mb or so.

Today I started getting the toxic "Code execution has been interrupted" message and realized that it had been a long while since doing "the save" on the other service pack version of excel.

I saved the workbook on the version of excel with no service packs. Then, without rebooting or adding any code the "Code execution has been interrupted" stopped.

Over the years I have found that saving a workbook on excel installations differing service pack levels has been the solution to many issues.

Hope this helps.

 

[landonaaronp]

Over the years I have found that saving a workbook on excel installations differing service pack levels has been the solution to many issues.

Hope this helps.[/QUOTE]

I am still pretty sure that mine started having the code execution error after changing my security settings, but now that you mention it, it may be worth noting that I was using the Microsoft Office 2010 Beta for some time (with no problems and no execution errors), before I reinstalled office 2007 (as a matter of company policy, not my decision). I am pretty sure I used this macro after reinstalling Office 2007 without having the execution error, but I can't really be sure.

 

[okCoder]

I mostly work in 2003, but have saved stuff in 2007 and then went back to 2003, with all available service packs installed. Sometimes the references to the various libraries will be broken when you go back to an earlier version.

If you copy/paste the macro into a new workbook, and establish your references again, it fixes the issue in all cases (for me)

 

[jombi]

One of the solutions mentioned earlier--shutting down the machine and rebooting entirely, has worked for me. This is of course "The Nuclear Option".

I will try the 'no service pack' method, as I have Virtual PC installed and can maintain a fresh, no sp version of Excel for this. I think if this works it's a 'less nuclear' option and may the best option if one has virtual pc.
--Jim

 

[trevexcel2]

Well just out of interest: Maybe some of you have found new solutions, or some news on the problem? It appears to go way back to 2002 or so.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-comfficeffice" /><o></o>
<o></o>
To summarise again: The 'code interuption popup' appears while macros runs on any file.<o></o>
<o></o>
My own workplace has been hit by this now. My colleague has a spreadsheet with many links, but only about 10 VBA subs. We installed MS Office 2007 about 3 months ago. He got it often. I myself got it just once, hopefully it was a one-off! We use a 3<SUP>rd</SUP> party add-in but luckily the problem seems to be unrelated to add-ins. <o></o>
<o></o>
The cut and paste option didn’t work for us. --> Eventually we solved it by putting simply “Application.EnableCancelKey = xlDisabled” at the top of the code of the first sub that runs. J.<o></o>
<o></o>
Unfortunately this has to be done separately for each separate workbook that gives the problem. Of course this is because we’re fixing the symptom and not the problem. It seems only MicroSoft can fix the latter. I encourage them to do this, and send all my love and good wishes.<o></o>
<o></o>
I took the liberty of pasting a number of attempted remedies below from the web. My sincerest apologies if I'm quoting anybody without their permission.<o></o>
<o></o>
Well I'm holding thumbs I stay luckier than my colleague. At least it’s Friday.<o></o>
<o></o>
=================<o></o>
<o></o>
- Some manual actions:<o></o>
“Just hit f5 or press ‘continue’ till the end of the run.<o></o>
<o></o>
“When the code is interrupted... Click to debug the code and then hit ctrl + break.<o></o>
<o></o>
- Application.EnableCancelKey actions.<o></o>
“At the start of your code: Application.EnableCancelKey = xlDisabled (For Excel) or Application.EnableCancelKey = wdCancelDisabled (For Word) .”<o></o>
<o></o>
“Sub X ; Application.EnableCancelKey = XlEnableCancelKey.xlDisabled; Code; Application.EnableCancelKey = XlEnableCancelKey.xlInterrupt.); End Sub.”<o></o>
<o></o>
But: “When the macro finishes, the setting will be reset to it's default (even if you don't specify) so there is no need to change the setting back.”<o></o>
<o></o>
<o></o>
- Stop your worksheet from updating your links, while running macros.<o></o>
For example when an add-in updated a price on the sheet it would give the above error. He deleted the link from edit links.)<o></o>
<o></o>
- Service packs.<o></o>
<o></o>
Remove them i.e. work on windows, before certain service pack is installed.<o></o>
<o></o>
Save Excel files in between PC’s with differing service packs<o></o>
<o></o>
<o></o>
- Tools | Options | Security Tab | Macro Security button = medium<o></o>
<o></o>
<o></o>
- Simply copy & paste code.<o></o>
“deleting all code, saving, and then reinserting code seems to help some people”<o></o>
<o></o>
“cutting code out of modules, compiling and then pasting it back in etc.”<o></o>
<o></o>
“In order to actually trigger a rebuild, it is normally necessary to modify a line, and then move the cursor to the next line to flag the source code as modified (e.g. make a change, move cursor down, move cursor up and undo the change manually).”<o></o>
<o></o>
- Reboot PC<o></o>
<o></o>
- Repair and cleanup actions: ((As a layman I myself am scared of this though))<o></o>
<o></o>
Worked apparently: “I copied the workbook in windows explorer and I tried the "Repair Office" utility.”<o></o>
<o></o>
Didn’t help much it seems: Run Office’s “detect and repair”. Forgive my ignorance: Are they talking here about [Control panel \ configuration manager \ components \ repair]?<o></o>
<o></o>
“Google around on VBA Code Cleaners”<o></o>
<o></o>
Worked it looks: “This problem got solved by choosing REPAIR in Control Panel. I guess this explicitly re-registers some of Office's native COM components and does stuff that REINSTALL doesn't. I expect the latter just goes through a checklist and sometimes accepts what's there if it's already installed, maybe. I then had a separate issue with registering my own .NET dll for COM interop on the user's machine (despite this also working on other machines) though I think this was my error rather than Microsoft. Thanks again, I really appreciate it.”<o></o>
<o></o>
Attempt, didn’t work I think: “The usual things --- Run Rob Bovey's VBA Code Cleaner on your VBA Code - remove all addins on the users PC, particularly COM and .NET addins - Delete all the users .EXD files (MSoft Update incompatibilities) - Run Excel Detect & Repair on the users system - check the size of the user's .xlb file (should be 20-30K) - Reboot then delete all the users Temp files.”<o></o>
<o></o>
<o></o>
- Re-install Excel <o></o>
<o></o>
<o></o>
- MS Access : you open the .mdb file via a shortcut with the /decompile option (an undocumented option).<o></o>
<o></o>
<o></o>
- Of course a good habit anyway is to always put ‘option explicit’ at the top of all your VBA subs. (It happens automatically if you choose [tools \ options \ require variable checking].) But this did not help us with the problem.<o></o>
<o></o>

 

[cokeguzzler]

I have been experiencing this problem for a while now. On my current pc and my previous one. After reading all I could on this issue on other message boards as well as those here I have been able to solve my problem.

For me the problem always resulted from the same action - using ctrl break to interrupt a macro. This would mean that I would randomly get "Code execution has been interrupted" when certain macros are run from that point on until a reboot takes place. The "Code execution has been interrupted" would take me to various places in the code, no problems are in the code and the code has been run thousands of times.

The solution
When the "Code execution has been interrupted" dialogue box appears hit debug and then hit ctrl break again (sometimes it required ctrl break to be hit more than once). This seems to reset what ever setting within excel was set after the first ctrl break.

Thank you for all those who enabled me to get to the solution especially akforsyt.

 

[trevexcel2]

Thank you so much! It seems to appear under my list of remedies but only now that you've explained it, do I understand what the person meant. My friend tried it and it worked as well. Thanks also to user "akforsyt".

 

[Proph]

I hate to post again on this thread which is several months old but I have had this same issue and seem to have found a solution. This problem is the most frustrating thing I have seen while using VBA. There is no reason for the code to be interrupted. The code can be perfectly written and yet you will get "Code execution has been interrupted."

I did not restart my computer, or even excel. I have not deleted any add-ins.
I am using Excel 2007 on Windows XP.

The simple thing that seemed to fix the issue for me... When the code is interrupted... Click to debug the code and then hit ctrl + break.

When you run the code again, it will work fine. Hopefully this will work for others as well.

This did it for me thank you for posting this.

Preston

 

[DamageZ]

The simple thing that seemed to fix the issue for me... When the code is interrupted... Click to debug the code and then hit ctrl + break.
When you run the code again, it will work fine. Hopefully this will work for others as well.

This worked a treat for me

I experienced this problem for the first time this morning. I am running Excel 2010 on Windows Vista. I have yet to restart my PC or even close Excel from the first time this happened. I have only checked the internet for answers.

 

[Ed in Aus]

Finally a solution to this problem... only been having this issue for a few years, on different versions, pc's, laptops... simple as Debug then CTRL+BREAK and re run the code.