Keep in mind that turning off warnings can be dangerous to your health. If you inadvertently leave the warnings off, you could easily end up loosing hours worth of work if you simply close an object you modified without saving it first.
To avoid the issue, I actually use two macros (the ONLY macros in my applications). One macro sets warnings Off AND turns the hourglass on and the other sets warnings on and turns the hourglass off. Then I run the appropriate macro. Using this technique, if during testing, I accidentally bypass the code that turns the warnings back on or forget to actually code it, the hourglass stays on. The hourglass being on is sufficiently annoying to jar me into running the macro to turn warnings back on and tracking down the issue if it was the result of sloppy coding rather than forgetfulness.
