Nom du Keyboard writes "As Microsoft drops support for older Office file formats, it looks like Visual Basic for Applications (VBA) is also going soon. Mac Office 2008 has dropped it in favor of enhanced support for AppleScript, and Office 2009 is scheduled to lose it in favor of Mac incompatible Visual Studio Tools for Applications (VSTA) or Visual Studio Tools for Office (VSTO). This sounds like the Mother of All Backwards and Cross-Platform Incompatibilities — especially since there appears to be no transition period where both the old and new scripting languages will be simultaneously supported. And as past experience with Visual Studio.NET has shown, upgrade tools are far less than perfect. So is Microsoft shooting themselves in the upgrade foot here?"
This discussion was created for logged-in users only, but now has been archived.
No new comments can be posted.
Good, about bloody time. The hardest bit of migrating users from Windows is invariably the crappy VBA apps they use, usually with a Access backend that doesn't handle multiple users.
I dread to think of what they'll replace it with, though.
Well, I was one to be developing VBA Apps as needed based on user shoestring budgets and technology needs. I was able to maintain multi-user environments in Access as well. Granted, they were high maintenance, but I got the job done.
If anything, it seems like this pushes the envelope to expand one's knowledge into other technologies that are more powerful, flexible and upgradeable.
I wonder if Microsoft is thinking of dropping support for other languages soon?
Hooray (Score:2)
I dread to think of what they'll replace it with, though.
VBA Apps (Score:1)
If anything, it seems like this pushes the envelope to expand one's knowledge into other technologies that are more powerful, flexible and upgradeable.
I wonder if Microsoft is thinking of dropping support for other languages soon?