Please provide a meaningful value (other than the current " ") for the Name property of the Commandbar object representing the shortcut menu which comes up when you right-click the very top of a Form open in Form mode (and ditto for reports) so that this can easily be disabled in code. It is currently one of three Commandbars with no meaningful Name.

The Host OS is unable to locate or use the ACE engine drivers for purposes of out-of-process automation calls, or ODBC connections when Office is deployed under Click-to-Run deployment models. This needs to be corrected so that out-of-process automation and ODBC calls can succeed no matter which deployment model is selected for deployment of Office/MS-Access components.

In Access 2007 and 2010, the Database Documenter returns the wrong value for Query RecordsetTypes.

If a query has the Recordset Type set to 'Snapshot' in the Design view, the Database Documenter reports that the Recordset Type is 'Dynaset (Inconsistent Updates)'.

If a query has the Recordset Type set to 'Dynaset (Inconsistent Updates)', the Database Documenter reports that the Recordset Type is '0' (which I believe is the value for 'Dynaset').

Setting the Recordset Type to 'Dynaset' does return the correct value in the Database Documenter, but this is the only setting to do so.

Enable the image control in form and reports show all kinds of images stored in database in app office365 (SQL). Currently error occurs and the image is not displayed. Using third-party ActiveX contoles, works.

I had some issues with a database. Getting messages like "file is missing". To get rid of it I opened a new database and imported all from the first one. After that the database works just fine, but colors on buttons changed.

The two databases, the "original" and the "imported" has Office Standards Theme. I cant find anything in settings that could explain the different colors.

On Access developers forum people found this issue still exists in version 2016. I use 2013.

Similar to what you have in macro design view. And please, a keystroke equivalent! Thank you.

return the current object status bar display during Database Documenter

Since Access Services is become the Ad Hoc RDB tool for BI it would be great to have Access share DAX features and functions as many of the functions in DAX could be used to clean-up and transform data for Power BI to visualize (e.g., Relate, RelateTable, Value, etc.

Currently ACCESS Services has datasheet view and QBE, why not SQL view like Access Desktop given its a Azure backend it would only make sense.

It would be nice to have some sort of indicator on the tab bar that shows if a query/table/... has been modified without saving, like a star "*" at the end of the name.

For a subform control, add a property to allow tabbing to next control on main form when at the end of the record(s) in the subform. This will allow for seamless tabbing from the user instead of one of the following:
1) having to know about ctrl+tab
2) requiring a mouse to get out of a subform and back to the main form
3) adding a work-around by adding a control and coding in VBA to setfocus back to the next control on the main form

When using the summary row in a DataGrid-view with SQL-Server-tables or views the Aggregate is build on the clientside, which is very slow when rowcount is high. Continually all rows are fetched to build summary. When ready, it starts again.

Please use sum(), avg()...-Aggregate-functions to get the summary.

Add some basic restrictions/rules to text fields like
- numbers only (incl./excl. .,+-< >)
- only characters ... allowed
-- like a to z, A to Z, ABC, incl./excl. language specifics (like ü û)
- entry must be between (1 to 999, 427 to 634, AAA to BBB)

Also add some basic formatting like
- convert to lower case
- convert to upper case
- convert to web-compatible
- convert to date/time (enter 290416 to get 29.04.2016 or 1534 to get 15:34)
- convert using Word rules
- convert to ... (EBCDIC, Codepage xyz, Unicode...)

it would be great if Access files would not Change the size so othen (bloat) and if the file size could be reduced. This would minimize Performance issues with different Virus Scanners and other issues.

With datasheets I often display system fields with a Grey background to visually indicate these cannot be edited. It would be great if we could set the BackColor Property of a Datasheet Field!

Probably impossible. But would have made a big difference to me while learning! Had slightly different versions of many of the same routines in several different apps before I even realized what was happening; took a very long time to separate back out.

Split forms with Pop Up property set to yes will do nothing when trying to use VBA code Form.Move Method.

Docmd.MoveSize Method works, but not Form.Move Method.

This condition has been verified by multiple users via UtterAccess Forum.