"code execution has been interrupted " message

R

robert phillips

New Member

Joined

Sep 15, 2007

Messages

43

• Sep 15, 2007

• #2

cray,

I know this isn't much help, but you may need to check that all the functions you're using from your 2k macros still exist in their same form in your excel 2002. MS often has a list of changes to the vba system with upgrades.

robert phillips

 

Upvote 0

R

robert phillips

New Member

Joined

Sep 15, 2007

Messages

43

• Sep 15, 2007

• #3

Sorry just thought of something else,

Did you try uninstalling SP3? There may be other system components affecting vba or excel due to component/dll version issues.... Maybe uninstall/reinstall sp3 and test again. Not pretty, but I've had that happen with other M$ updates....

robert phillips

 

Upvote 0

C

cray

New Member

Joined

Aug 24, 2007

Messages

2

• Sep 17, 2007

• #4

Code Execution has been interrupted

Sorry just thought of something else,

Did you try uninstalling SP3? There may be other system components affecting vba or excel due to component/dll version issues.... Maybe uninstall/reinstall sp3 and test again. Not pretty, but I've had that happen with other M$ updates....

robert phillips

Click to expand...

The compiler does to alert me to any errors so I assume the upgraded Excel VBA is compatable. It's a business machine and I am not allowed to uninstall softwate . Our local IT support eont touch this problem.

 

Upvote 0

J

Jsmooth65

New Member

Joined

Oct 1, 2007

Messages

1

• Oct 1, 2007

• #5

I've been having this same problem with many macros I create. I just fixed it today (fingers crossed). Try putting this in the first line of your macro.

Application.EnableCancelKey = xlDisabled


You won't be able to use the Esc key but just ctrlaltdel to break. So far, its fixed my random "code execution.." errors.

 

Upvote 0

L

lneer

New Member

Joined

Oct 8, 2007

Messages

2

• Oct 8, 2007

• #6

I just started getting this today after installing Visual Studio 2005 on a Vista computer. Whole bunch of my excel macros throw this message up at some program lines. I don't see the pattern to it yet.

Adding the "Application.EnableCancelKey = xlDisabled" line (mentioned above) fixes it.

Seems like a noxious bug.

 

Upvote 0

L

lneer

New Member

Joined

Oct 8, 2007

Messages

2

• Oct 9, 2007

• #7

Forgot to mention

The macros that broke after I installed Visual Studio 2005 (plus patching it fully) all worked on the same Vista computer a few days ago *before* installing Visual Studio.

Unfortunately, removing Visual Studio did not undo the damage....

 

Upvote 0

E

ejs7597

New Member

Joined

Sep 25, 2006

Messages

35

• Jan 28, 2008

• #8

Should we re-enable the CancelKey at the end of the Macro?

Application.EnableCancelKey = xlDisabled

Application.EnableCancelKey = xlEnabled?

 

Upvote 0

X

XL Merrill

New Member

Joined

Feb 13, 2008

Messages

1

• Feb 13, 2008

• #9

the three options for Application.EnableCancelKey are:
xlDisabled -> which ignores pressed keys and solves the problem
xlInterrupt -> which sets the error handleing back to Excel's control
xlErrorHandler -> wich makes error go to your error handleing section

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 unless you want to re-enable user breaking during part of the macro run.

 

Upvote 0

J

jimv

New Member

Joined

Feb 12, 2008

Messages

46

• Feb 29, 2008

• #10

XL,
Thanks for that code. I too have been having same problem and this fixed it.

 

Upvote 0