isladogs
MVP / VIP
- Local time
- Today, 03:47
- Joined
- Jan 14, 2017
- Messages
- 19,253
I don’t agree about this being a valid concern.
Although I don’t agree with the decision to remove VBA support from New Outlook, it was a somewhat unique case.
Over the years MS had created multiple versions of Outlook, for PC and Mac, both desktop based and web based. This meant there were multiple code bases to maintain which was expensive in terms of developer time. The Office Watch blog has written about this extensively.
Rationalising all of those into a single code base made sense, even though the end result is far from satisfactory as far as developers in Access/Excel etc are concerned.
Access is different. It is desktop PC only. One code base only. One of its main selling points is its ability to work with a very wide variety of file formats using automation. Removing that functionality would completely change its purpose in a negative way and have no financial benefit for MS. Therefore it won’t happen
Although I don’t agree with the decision to remove VBA support from New Outlook, it was a somewhat unique case.
Over the years MS had created multiple versions of Outlook, for PC and Mac, both desktop based and web based. This meant there were multiple code bases to maintain which was expensive in terms of developer time. The Office Watch blog has written about this extensively.
Rationalising all of those into a single code base made sense, even though the end result is far from satisfactory as far as developers in Access/Excel etc are concerned.
Access is different. It is desktop PC only. One code base only. One of its main selling points is its ability to work with a very wide variety of file formats using automation. Removing that functionality would completely change its purpose in a negative way and have no financial benefit for MS. Therefore it won’t happen
