The Filter Value List in datasheets is set to scan the full recordset's field to display a unique list. This takes time and i/o in a pure .accdb recordsource and worse, will not work if the recordset is based directly on an ODBC attached source.

Many Filter Value Lists are sourced from fields which are foreign keys to look up tables - we could intervene by feeding the look up table as source for the Filter Value List.

When I try to export an Access table into an Oracle database it doesn't retain the input field formats. Everything is converted into a string and the indices are lost. I've contacted Microsoft about this before but got no meaningful response, presumably for petty proprietary reasons.

For examples, it frustrates to me when Access decides to trial run my complicated or data intense cross-tab queries upon entering or exiting design mode. And sometimes it alters a failed query automatically when I open it in design mode. In all cases the auto changes are destructive, even when I try to close out of design without saving. There are many other automatic features for dummies that I'd love to disconnect but can't.

This new SKU would be welcomed by Enterprise IT departments and the professional development community if it lives up to their expectations. You can also charge a subscription or one-time payment for the Access Enterprise runtime's in order to fund the improvements we've requested in this site.

Access 2007 added the Rich Text control so we can store rich formatted text in Access. What it forgot to add was an easy way to share that formatted text in Excel or Word. Please add a means to share the rich text data in at least other Office apps and a easy way to strip the formmatting when exporting to formats like .csv.

In earlier version of Access, when you modified a query the context menu had the choices of “Save”, “Save As…” and “Close” in the context menu. Since the ribbon was introduced, the context menu only provides “Save” and “Close”, if you’ve made a change in the query and don’t want to over write the existing one, you have to go to the File | Save Object As route to get to the “Save As..” dialog box.

It's hard to find things if you don't know the exact name in english if you search some things - especially because Help doesn't work / help.

Why not enableing the user to select "selected" columns / rows via Query - always looping thru itemselected is not very easy and intuitive.

Similar is with queries about Tables, queries, forms, reports, indizes fields (like in combobox) and Macros and all the other collections.

If you select values via combobox (you open it to show a list of values) then i often want to restrict what is shown there, but if combobox is "closed" (just the result is shown) then i do not want to apply any restriction there. (When closed Show "Select Names form tblAdress" but for show selection: SELECT Names from tblAdress WHERE dept = 1; ) ...

It would be more intuitive to link sql tables WITHOUT the owner prefix.

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

Java Driver
please create a driver for java, so that it would be able to create a android frontend to accdb-databases

Windows 10 in particular like to highlight controls as you pass over them. This capability should be available for any control and would also be very useful on a continuous form to highlight a particular row as you mouse over.

I have noticed this issue whereby you move columns and when the user exits the form, the datasheet columns revert back to the original (pre-saved) order. The work around I found was to hide/show columns, toggle one field on then off, close dialogue and then it will save. Not very intuitive.

Thanks for fixing.

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.

The error object should be expanded to included properties which can reveal the procedure, module, and object that the error is taking place in.

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.