Quote:
Originally Posted by Guessed
Also, note that someone hacking the .bas file is not in itself a risk since the macro won't run there. However, if you subsequently take those .bas files without reviewing for un-authorised changes and drop them into a template/document then the risk could be realised.
I would be more worried about someone hacking the code which is also in the MS Office file that the .bas file came from. This is a much more direct risk.
|
In my company, we've had Word macros stored in .bas files on a shared drive for decades. That's why I'm a bit concerned—it's 2025 now, and anyone can create macros or use other programming tools without much restriction. Plus, my colleagues often tweak the code to suit temporary needs. The macros are pretty lengthy, and we just don’t have the time to review and check each one individually.
And you're absolutely right—someone hacking the code in the actual MS Office file (where the .bas file came from) is a much more direct risk. That’s something I really need to keep an eye on.
