When one creates an accde database, Ms access 2007 SP3 up to 2016 should also remove the ability to modify tables and queries.

There should be a feature to disable the ability to export all objects in access 2007 SP3 up to access 2016 desktop database, regardless whether the database is passworded or not.

And/or make it a permantent setting for all new databases after an user has change these settings

No explanation needed i guess.

Create a new type of VBA add-in (*.accda) that loads before the database is loaded, can display its own ribbon and is unloaded after the database is unloaded. This would enable VBA programmers to build application add-ins like in Excel or Word.

Take on IBM SPSS Modeler. For example, work with the developers of R Statistical Computing to provide regression, clustering and neural network functions. At the very least extend the Domain Aggregate functionality to include a percentile capability.

When we use the expression builder, the middle column (expression categories) currently does not sort alphabetically so it makes it time consuming to search for controls.

how wonderful it would be to have programmatic access to create forms and Controls at runtime (compiled version)
Even The ability to create and change reports.

I would think after all these years MS has a pretty good knowldge about reasons for file corruption. It is quite the joy when The dreaded dialog that deletes Your vba Project appears...

When using the Button wizard MS Access creates macroes as default. This should be an option if you prefeer macroes or vb as the event code.

Too many queries fail for obscure reasons. E.g., a crosstab that has a subquery somewhere in it. I bet there are already open defect on a lot of these issues from the JET days. Work them! Limitations like the 32 table limitation occasionally get in the way as well.

(Again hating to spend votes on defects, but it is what it is.)

Need to clean up all the UI to scale properly on high DPI displays. E.g., Navigation pane vertical object spacing, low res navigation pane object and navigation (expand/contract) icons, and "Save changes to the following objects" dialog box.

(Hate to spend precious votes on what is basically a set of defects, but there it is.)

In VBA, we can only store nulls in a Variant data type. But I hate this because this lacks information whether this is a string, a number or date. In SQL, those data types are all nullable but we have to constantly do Nz(), IsNull(), to avoid the nefarious error "Invalid use of Null".

Please make it possible for us to specify a nullable data type so that we also know this can be only either a null or a number (and thus prevent invalid entries of string in addition to writing self-documenting code).

Is it really necessary to re-arrange the column order when I save a query? It tells me MS Access is reducing the QBE grid entries into SQL, optimizing that syntax and when asked for it later the presentation looks scrambled. While this may be needed internally, how much harder can it be to ask the internals to remember the column order?

Do NOT have ANY dialog boxes that are limited in size, esp. when they open modally (do not let you click outside their zone of control).
Linked Table Manager is one. Library File management dialog box is another (where we go to tell it where a new or missing dll file is located). There are others. Simply stop using this very old protocol.

In print preview and normal view, if a supreport is empty, it gets hidden. Please do the same for Report view.

Instead of manual ctl-A, Ctl-c, open excel, new worksheet, ctl-v.