Debugging Visual Basic for Applications - Office 2010

Am I missing something ?
I'm writing some very simple VBA in Office 2010 - tinkering with powerpoint at the moment

When I run the code and its correct then its all fine - what I find really irritating and takes up a lot of my time is debugging.

When I've wriitten code in the past and there was an error then the program would stop - a message box would appear explaining the error, the code would 'break' and the code window would appear with the offending line highlighted in yellow. I liked this !

Now when an error occurs in Office (Powerpoint - but it think its the same with all apps), there is no message box, the code does not 'break' and no code window or highlight appears. The only indication that there is a problem is that the expected actions do not happen, it seems that errors are silent - this makes tracking down the source of problems very tricky indeed,

Can Office 2010 VBA be made do show errors the way previous versions used to ?

I've gone to Tools->Options->General on the VBA screen and set 'Break on all Errors' - but without any affect.

Yesterday I has a problem with a badly formed filename - a run-time error  - it took me 3hrs to find out what the problem was, once I'd located the issue it only took a couple of seconds to fix it - I need to work more productively and be able to locate errors more efficiently.
LVL 70
Brian PiercePhotographerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Richard DanekeTrainerCommented:
When you test your VBA with a run from the VBA editor, I think you will see this.
You can step thru the code, use the Immediates window, a watch window, etc. to test before running in  PowerPoint.
Brian PiercePhotographerAuthor Commented:
Tried that - but can't do some things as some of the code relies on a sheet/slide/document being open on-screen.

Am I the only person ith these issues ?? how do others effeicently debug VBA ?
Brian PiercePhotographerAuthor Commented:
anyone ?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Brian PiercePhotographerAuthor Commented:
No solution
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.