Many MANY users aren’t aware of VBA or they don’t understand it. Truly, the Numero Uno reason for avoiding (or limiting) use of VBA: If you don’t use good comments in your code, you’ll struggle to understand your own work if you have to revisit it weeks or months later. If the macro is designed to delete information and you run the macro at the wrong time or, the code is wrong and deletes work you spent hours creating … ! You’ll look up and see the UN-DO arrow grayed out. There is no UN-DO! This bears repeating: There is no UN-DO! Some users freak out when they open the workbook and see the security warning about enabling macros. The VBA code has to be manually modified, or you just live with the sheet being called February. VBA does not adjust in the way that formulae do when you move data from one worksheet to another, insert a column, delete rows, etc.Įxample: you have a sheet called February.
Sometimes writing, testing and debugging the script will take longer than using worksheet features. There are good reasons to avoid (or at least be cautious about) using VBA. It’s seductive to start thinking in VBA and head straight to the VBA editor with every task.
I’ve used VBA to break the passwords on other spreadsheets.
The power that’s available is almost frightening.