I'm not dead yet! I don't want to go on that cart!!
I remember thinking "Isn't that a security risk?" when I first heard about VBA. We did not have to wait long for confirmation. It is worrying that they still haven't put a sufficiently tight sandbox around VBA. I can see reasons to use macros within a document (I have used for loops and while loops in LaTeX at times), but I see no reason why code within a document should ever be allowed to alter template files or indeed any other file on disk (except the printed, postscript, or pdf output) which outweighs the security risks involved.
Biting the hand that feeds IT
