Excel 2010 debugging problem

[Jaye7]

My work was kind enough to give me excel 2010 when my old computer died and it is annoying me as the debugging of VBA is atrocious compared to the 2000 version.

It seems that whenever a macro has an error rather than the debugging function popping up excel just decides it needs to close, simple errors too, like a textbox is missing etc...

Does anyone know of a way to make it more stable with scripts so that it goes to debugging rather than just closing which is annoying as then you have no idea what script caused it to close.

Thanks

 

[shg]

I don't have Excel 2010, but if this code is in a Forms module, try Tools > Options > General, tick Break in Class Module

 

[Jaye7]

Thanks SHG, that was the first thing that I tried but unfortuantely the timer keeps running.

 

[shg]

Timer? What timer??

Did I miss something???

 

[Jaye7]

Sorry my bad, I was thinking of another question I asked. I have now ticked the break code and will see how it goes.

thanks SHG

 

[Jaye7]

Unfortunately this didn't work, it still crashes constantly on basic errors, what a pain in the neck it is.

If you spell a textbox wrong (i.e. texbox) when writing script, look out as excel 2010 usually crashes (for me anyway).

I didn't want an upgrade as I love 2000 version, oh well, that's life, just have to suck it up buttercup.