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).

When using the tabbed interface, if you switch a form out of Form view to Design view, the interface changes to the next tab in the sequence. You have to manually re-select the tab you were working on each time, which is really annoying. This bug affects all versions that support the tabbed interface, from what I have observed.

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.

If you have set your nav pane options to show system objects, they should not show in the Import list.

When creating objects such as forms and reports it would useful to be able to have a dialogue form where you can key in notes and a date to keep documentation current. Have a few columns for date, user notes and developer notes. On the ribbon, have a notes icon which will open the notes to the current object for display and edit. Have it link to the ID Field in Msysobject table.

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

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

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.

Better control of datatypes when importing from Excel or linking to a worksheet.

Currently the import decides for you using the first few rows, so often you have truncated memo fields when the first few rows are less than 255 char or errors when the first few rows are numeric but later rows are alpha numeric.

When importing into an existing table the import should honor the datatypes in the table.

No explanation needed i guess.

Perhaps like a sql server log file, create a file of with error messages using err.object properties but the records must include application db, user, date/time, object(access object), module, procedure.

Let us know when we can download it

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.

Many of the error messages could be more informative. Those that tell us 'it was not possible to xxxx nn records' could provide information in a table about which records had the problem - like you get with type conversion errors on an import.

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.

wpf/xaml Controls and Windows

allow to insert wpf/xaml Windows to be placed in the forms-container.
so developers can switch partially the accdb apps to new databases