We have a webservice on which we have a PowerApp connector that enables PowerApps to run any macro, vba procedure/function, opening of a form to fill in text-fields and/or perform the equivalent to buttonclick-events in an Access Application. If MS-Access out of the box could configure and enable a webservice on the machine it's running and thus would enable a PowerApp to be a cloudfirst/mobilefirst frontend presentation layer, MS-Access 2019 would really become something new. When the Access application has linked SQL-tables to SQL-2016 or up, it can easily delegate the creation of JSON to SQL-server, but I wouldn't be surprised VBA already has JSON functionality in Access 2019.

Access needs a quick way to get a good solid installation of Back-end and Front-end databases including a registry edit for Trusted locations and versioning.
It should also include the ability to:
Add Icons,
Add Desktop and other shortcuts,
Allow user to accept an ELUA (End User License Agreement)
Run simple scripts,
Install with full windows trust. (maybe with a certificate?)
An uninstaller.
A check for updates function.
Install support files into specified folders.
Read simple system values and react accordingly (eg if 64bit systems then install 64 bit ODBC Driver)

Also it would be nice if it could notify the user of a new application Version (via a Web ini file or similar?)
Optionally install the Access Runtime.

This would lead to massive time saving for developers and make installations quick and identical across many users...

'~~~~~~~~~~~~~~~~
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.....

Many folks misunderstand the "w" interval setting used in the DateDiff() expression. The MS Access help file indicates that this interval is for "Weekdays". To some the term "Weekdays" means "Workdays" (ie: Monday through Friday), thus the confusion and claim that the "w" interval does not work. But the term "Weekdays" (thus the interval "w") means an indicated day of the week.
o ... with an expression like:
DateDiff("w", #4/1/2008#, #4/30/2008#)
The returned result is 4. Access looks at the start date of the indicated span and determines the day of the week the start date falls on, which is Tuesday in this case. Access will then count the number of Tuesdays between the dates indicated, note that the start date is NOT included in the count.
Other samples:
DateDiff("w", #4/2/2008#, #4/30/2008#)
-- returns 4 (the number of Wednesdays between the two dates)
DateDiff("w", #4/3/2008#, #4/16/2008#)
-- returns 1 (the number of Thursdays between the two dates)
{As a side note, the similar interval "ww" simply returns the number of Sundays between a date span.}
.....
Knowing how the "w" interval works can be quite handy when doing date calculations ...
For example, here are two archive posts that utilize the "w" interval of DateDiff():
fNetWorkdays() and fAddWorkdays()
fCountWeekdays()
Orealize that this little bit of information is touched on in the Access help file on the DateDiff() function, but with the confusion that is often associated around the "w" interval, I thought it was worth expanding upon. I hope you have found this information helpful. thumbup.gif