• Subject: Re: looping through inbox messages / debugger under Outlook VBA
  • Author: Mark VII
  • Date: 09 Apr
  • References: 1 2
Hi Ken --

One thing I'd already tried was to have a rule that invokes a sub, and the
sub calles the procedure that does the actual processing. Neither F5 for
breakpoint nor Stop statements worked there.

FWIW, I started with the processing logic in the sub invoked by the rule,
same results.

Interestingly, if I invoke the sub that does the actual processing from the
Immediate Window, breakpoints work like they should.

One thing I didn't mention is that I had been kicking off my rule from the
"run rules now" part of the Rules and Alerts dialog. Wonder if that's making
a difference, because there a dialog open.

Any thoughts in light of that?

Thanks,
Mark
09 Aprlooping through inbox messages / debugger under Outlook VBA.Mark VII
09 Apr|- Re: looping through inbox messages / debugger under Outlook VBA.Ken Slovak - [MVP - O...
09 Apr|  \ Re: looping through inbox messages / debugger under Outlook VBA.Mark VII
10 Apr|     \ Re: looping through inbox messages / debugger under Outlook VBA.Ken Slovak - [MVP - O...
09 Apr\ Re: looping through inbox messages / debugger under Outlook VBA.Sue Mosher [MVP-Outlook]
10 Apr   \ Re: looping through inbox messages / debugger under Outlook VBA.Mark VII
10 Apr      \ Re: looping through inbox messages / debugger under Outlook VBA.Sue Mosher [MVP-Outlook]
10 Apr         \ Re: looping through inbox messages / debugger under Outlook VBA.Mark VII
All times are in (US) Eastern Daylight Time (GMT -4:00)