Karl-WE
and
Neil Jordan
I agree with your feelings of concern for the direction that Microsoft seem to be moving, and the way that they are doing that.
I have been seeing lots of declarations re the intent to replace VBA, with scripts, or other Microsoft profferings.
But - I then find that while VBA was available for use throughout the Office applications, and at all Licence levels, Scripts is apparently only available to those with a corporate level licence, and business version of OneDrive, and, when someone actively tries to start learning the language and needed techniques, they find that it also only seems to be accessible through the Excel App.
Basically - Microsoft seem intent on stopping the general public from using any automation facilities.
Regarding Access - that seems to be getting some additional features, and a few fixes, but nowhere near the attention and improvements in facilities being forced on users of the other Office Apps.
OK, maybe the stability is a "pro" rather than a "con" point.
Regarding VBA experienced staff -
I am a self-taught technician, starting in the early 90's, having discovered the forms based facilities for data entry validation, as well as the data management facilities available trough SQL making it a much better approach to data handling in corporate environments than Excel, and freeing user departments from the need to get the IT specialist staff, or 3rd parties to do all the coding and associated work.
There are many people with VBA experience, and many adopting self-tutoring despite the MS attitude guiding them away from VBA.
The currently still excellent accessibility of VBA, meaning that self-learning is possible with a minimal PC system means that those organisations wanting VBA should find it easy to get experienced contractors and training for new staff.
And the ease of moving Access based data to larger server systems, while keeping front-end facilities almost unchanged should keep it in use as long as Microsoft do not depreciate its facilities and availability from the currently easy and relatively inexpensive acquisition and implementation state.
So - MS, please please do not move away from supporting VBA in all the Office Apps, and, if you want scripts to become prevalent - make it accessible to, and usable in the same environments as VBA, while, to stop forcing users to Oracle, and other data management facilities and front end data access.
And - towards that -
Please detail an ongoing future for VBA, and Access !
And then publish those future prospects.