It'll only run on cloud. Their employer would probably block that too.

Afaik the python is ran on Microsoft servers, so not exactly a perfect solution. I doubt it will run offline at all

Wouldn't it face the exact same security issues as VBA, with drive-by installs of obfuscated malware and executions of arbitrary code?

It is their own Adobe Flash

No, that was Silverlight. VBS is MS's JS.

Can confirm. Worked at several billion dollar corps that would collapse without vba.

Another confirmation here. At my previous job, I was they guy who built Access databases and wrote VBA code. While not ideal, it was a very small business (less than 10 employees) and it was fit for purpose.

When I got a new job at a company with almost 3,000 employees, I was like, "Finally, I'll be working somewhere that has proper IT resources." Ha! I soon find out that my department runs critical business infrastructure with Excel macros. And we have a proper IT department.

As everyone has already said, if IT resources are in short supply (or the wait is too long, or building projects with IT support is a PITA), then people will build systems with the tools they have at hand. And that's often MS Office.

I've worked for a major international company and I was for a while the only maintainer of a shitty request form in an excel file, sent worldwide to hundreds of people. As they wanted more and more specific functions the stuff grew to thousands of unholy VBA code lines and a huge hidden sheet of data.

That thing even had a fully custom language switch function for all dozens of field labels and their possible values.

I kinda hope they're still using it (that wouldn't surprise me) and that their whole workflow will crash and burn when Microsoft finally kills VBA.

MS: You have until (now +2 years) to phase out VBA.

Enterprise: panic noises

Enterprise will cause a boom in hiring VBA devs to migrate legacy apps to other programming languages, then hear Microsoft will extend support for a few more years, then fire all those VBA devs again. If Microsoft had some wits, they'd create easy tools to migrate VBA to C#.

Well it's gotta be done some time... otherwise we end up with another version of COBOL.

Yup that's normal because VBA is single-threaded, doesn't take advantage of vector instructions and even its interpreter is slow. So when someone writes numerical code in VBA working in single precision, and assuming they have an 8 core CPU with AVX2, they're using only 1/64-th of their CPU's processing power. On the other hand with Python, while it's still interpreted, the interpreter is much faster on its own, and you have modules like numpy that use precompiled routines that take advantage of vector instructions (and possibly multiple cores).

Btw, Libreoffice supports python scripts. Other offices too?

I don’t think there were any computers designed for K-12 schools at the time. They were PowerMacs, and later, iMacs. They weren’t even set up for multi-user; they were just unlocked all the time.