Forum Discussion
Macro Type Error
I just upgraded to Office 365 and now one of my macros is generating a Type Mismatch error. The macro is pasted below, and the offending code is highlighted in red, bold italics. I would greatly appr...
I think you can forgo the VBA and just use conditional formatting for this.
Nevertheless, if the VBA is important, then I would recommend a couple of things to straighten this out:
1) add Option Explicit to the top of the module - this will force you to declare all variables and reduce the likelihood of type errors, or at least increase your chances of avoiding them in the first place
2) dim processed as boolean
3) dim paid as boolean
4) Don't use separate variables for NotProcessed and NotPaid. If you dim processed and paid as boolean, you can just:
If processed and Not paid Then
... etc
Nevertheless, if the VBA is important, then I would recommend a couple of things to straighten this out:
1) add Option Explicit to the top of the module - this will force you to declare all variables and reduce the likelihood of type errors, or at least increase your chances of avoiding them in the first place
2) dim processed as boolean
3) dim paid as boolean
4) Don't use separate variables for NotProcessed and NotPaid. If you dim processed and paid as boolean, you can just:
If processed and Not paid Then
... etc
Thank you for your excellent suggestions! I hadn't thought about Conditional Formatting, but that's a great recommendation.
Declaring variables in one location is also a good habit, in fact, back in the day when I was a programmer, that was always my style and recommendation. However, I'm not a VBA programmer and typically fly by the seat of my pants! With that said, I changed all my variables to "variant" and that seems to work.
Thanks again for your comments and suggestions!!!