There’s enough Microsoft Office stuff out in the wild that relies on VBA that I think it unlikely that VBA will become unsupported before I retire.
I have noticed they keep trying to kill VBA. Some old (as in TWENTY YEARS OLD) macros have finally stopped working in a process that my group uses… and yeah, I wasn’t around when they originally created them. So yay! A chance to replace!
Funny story tho.
When I started my job, we had a python script that generated and sent about 50 emails every quarter. Then IT changed the settings of the Exchange server to only accept local connections from Outlook, so the code stopped working. So I rewrote it in VBC, which worked fine because it generated the emails in Outlook. So if they do replace VBA with Python, then I’d replace the VBC code I used to replace the Python code with Python code.
1 Like
The history of VisiCalc
