No.113001
finally... windows python programming...
No.113003
Can't wait for them to sunset VBA and destroy decades of barely documented code written by people who are long gone on which the entire operational capacity of the company depends on.
No.113004
>>113003they're simply creating new demand
No.113325
>>113000Does it even work on anything that isn't 365?
No.113338
>>113325eh? MS office rebranded as 365 so there is no alternative
No.113341
>>113338What? As
>>113003 pointed out a lot of companies, including mine, still work on old versions of MS office so as not to break the macros that were created years ago. I still use 2016 office and I know people who still use 2007.
No.113343
>>113341oh.
Well of course python won't work there.
Now company has reason to pay someone to rewrite it all in Azure python!
No.113345
>>113343>company>payUnless you're working for some huge conglomerate, that's not gonna happen. People in small companies mostly just add to the existing undocumented VBA macros for their convenience and none of us have time to rewrite it in some other language.
No.113347
>>113345figures. But there's always a time. Just like needing new equipment.
No.113351
>>113345>undocumented VBA macrosI like to document such things when I can...
No.113353
if undocumented decade old VBA macros are bad I will dread the state of things in a similar amount of time with Python
No.113357
Dont hoard your VisualBoyAdvance macros, people
No.113358
>>113000Didnt people used to make runescape bots with this
No.113359
>>113358Except it was java in excel
No.113363
>>113362A lot of viruses are written in VBA which is what the MS Office suite uses for user programming.
So perhaps someone did that and let it print bot statuses to the sheet
No.113401
>>113400Blocked. Hidden. Reported.
No.115152
>>113517As a strong start, future releases of Windows 11 will not only not install the Windows Scripting Host by default, but will deprecate VBScript altogether.
VBA is a whole different issue though.