'~~~~~~~~~~~~~~~~
VBA Native line numbering
'~~~~~~~~~~~~~~~~
Adding line numbers is something that is a pet peeve. Line numbers should be Native and error trappable by default without having to add them manually.

'~~~~~~~~~~~~~~~~~~~~
VBA Accessible Call Stack
'~~~~~~~~~~~~~~~~~~~~
A way to read from the call stack, function/sub names in order accessed, times accessed...etc

'~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
VBA Custom Toolbars to allow custom Macro/Function Calls
'~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If I could add my ow custom functions as a toolbar button and have my toolbar exportable and importable for others to use. As opposed to a full Add-In.

'~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
VBA button and/or right click to open SQL Editor
'~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Frequently I need to use an SQL editor to evaluate or build a SQL String and it takes time clicking through to a query then changing that over to an SQL editor screen.
This could be eleviated with a quick access button or right click method from ANYWHERE. Almost any commandbar could benifit from this added functionality.

'~~~~~~~~~~~~~~~~~~~~~~
VBA Higher Level Access
'~~~~~~~~~~~~~~~~~~~~~~
What I mean by this is a way to look down over the project as a whole. Functions such as onDatabaseClose() or countAllOpenExternalConnections().
Another use would be a public onOpen(byval ObjectName as String) Event that fires for all objects of a certain type. So Before a form opens and runs it's own onOpen event you
could run a higher level procedure to capture or set data without having to add any code at all to the forms onOpen Procedure. Obviously it would know very little about the
object being opened but none the less I can see uses for such a procedure.
....and more that I can't think of this second...

'~~~~~~~~~~~~~~~~~~~~
'Access Forms ListBox
'~~~~~~~~~~~~~~~~~~~~
A more robust Listbox, Native and with the ability to add icons and check boxes, colours,buttons,editable textfields, sort orders.
Sure you can add an ActiveX component but why not Native? Improve this usefull feature.

'~~~~~~~~~~~~~~~~~~~~~~~~~
Access Tab Controls
'~~~~~~~~~~~~~~~~~~~~~~~~~
Should be able to have tabs aligned horrizontally as well as vertically

'~~~~~~~~~~~~~~~~~~
more to come when I think of them.....

Changing to the new black theme and then closing out of access completely - re open access and change theme to colorful and the navigation search bar remains black, changing to grey and back to colorful also does not change the search bar back to white.

The black theme is a nice idea and aligns itself with windows themes and visual studio however the implementation leaves a lot to be desired. Disabled ribbon button labels are too dark and don't have enough contrast to be visible. Open a query editor window and try to read the labels in the bottom pane on the left hand side against the white background - this needs to be fixed. Relationship window with the black and white themes especially we are noticing the grey 1 - many symbols are practically impossible to see and the graphics engine seems to be creating horrible tearing when you create a relationship and move one of the tables in the window.

I would like to suggest to Microsoft an idea that came to me in a dream last night. My dream was a little bit like:
I was sitting in a bench at some park, there was no black people around, Donald Trump probably won the reelection. I was reading the news, "Elon Musk dies on his way to the sun"... For some reason I'm not surprised. All of the sudden I realize I was supposed to go to work because its sunday! I rush to McDonalds... on my way I see a massive screen showing the new capabilities of Access 2079 -"Amazing integration with Office 2007, Incomparable speed on deprecated processors, Almost ready for Hidpi, Still $100 a licence"
I'm in shock, this is not a dream, its a nightmare... this is the future and Access is still around, and MVPs from the 90s manage to put their brains inside machines so they could still scam people with their creations...

Please, deprecate Access, lets not fool each other, the only reason Access is still around is the same reason dBase and Cardbox and other near abandonware products are still around, because theres an old userbase that will rather die than to move into any newer technology and they serve a large number of small businesses in the PAST!

It has to go... think about it as a catastrophic incident, no one wants it to happen but it will happen, and if it happens people will just have to live with it. Just like Sharepoint, just like Silverlight...

I could create a PRG file that would perform much as an application ...
I am gradually learning the intracicies of ACCESS objects and how to build embedded queries inside of queries. I am also able to build some pretty exotic filters at this point. The Do While Loops coupled with nested If statements in DBASE enabled me to perform some pretty complex real world processing, that I find more n more complicated to replicate using ACCESS. It would be the BEST OF THE BEST if there was a bit of the same syntax as the Ashton Martin - DBASE. Or are they copyrighted?

OK I get it... you supposedly don't need to be a developer to use Access and that's great. But really you should stop training everyone who doesn't know any better that it's ok to do things like place spaces and weird character in object names. It will eventually bite you even within Access as soon as you move to VBA or a SQL Server backend.

Just because it can be done doesn't mean it should. It's just all around bad practice and eventually everyone who continues on to use Access will learn the hard lesson that is not taught in the books that you should not do this!

Hello
My post is a general post about which way should MS Access take in the future. I have used Access as a professional tool in my company against large and small companies from the early versions of Access. I believe that this is the most common use of Access although Microsoft from the beginning of the product have added this at the Office package as a low-threshold entry to the database worlds. Microsoft has reduced the availability of Access in its Office suites from early beginnings. In view of this, I mean Microsoft should let go of Access as part of Office package and develop a completely new "Access" software for the professionals.
The new “Access” is to be dedicated against the professional marked.
Having said this many will come up and ask why not use Visual Studio or other systems. To this, I reply that VS never built to a specific task as Access, but as a general toolbox that can handle an infinity of tasks.
What we need is a tool that is dedicated to the development of interfaces against professional databases ref MS Sql server and that only.
Microsoft could then develop from scratch a new professional tool without no boundaries to the old Access.
This software could contain of a desktop and a web version that could handle the future.