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.

There are two undocumented methods, SaveAsText and LoadFromText, which were originally used for the old SCC integration. Since Access 2013, the source code integration has been removed and we now rely on third party tools (e.g. OASIS-SVN or Ivercy being example). It is my understanding those still rely on the undocumented methods. This request is to ask that Access team document those methods and thus make it supported so that those tools can continue to count on it being available and provide a solution for source code without taking any resources from Microsoft.

Replace/remove Ribbons out of Access (or better out entire Office).
Nearly every, even the smallest little and tiny application has an better menu structure than this space taking ugly ribbon thing. Besides, now we must conclude that after 8 years of introduction there is still no decent ribbon builder included within Access it is time to get rid of it. Lets say, it was a nice try, but let's return to something better please.

I have never understood why after all the effort put into compiling Forms and Code in Compiled Access databases and then they leave the Navigation Pane exposed so that all Tables are revealed and accessible to end users. Sure you can hide the Navigation pane but anybody can go into Options and reveal that Pane.

This has been a major negative to Access for me for years ....

Dick

When a tablet or PC goes into sleep mode any active form looses its connection to the database backend (I am using SQL Server). This is very annoying in tablet environments where the PC is frequently switched to sleep mode. Make it so that Access can detect a reawaken from sleep and refresh the connection automatically rather than leave an error so that the user doesn't have to log off and reload the screen.

As per Excel, it would be great to highlight and distinguish field data between the records displayed. Currently, if a format is set on a field, in a continuous form, the entire column receives that format, whether or not the data value contained, matches the criteria.

The Adobe PDF-Format allows to implement form-fields. This fields could be filled in by the receiver of the PDF-File.

In my opinion it would be great to generate an PDF-File with Access with form-fields. If the data from Access could be pre-filled in, this would be great.

The generated PDF could then be sent via Email to a client. The missing data could be filled in direct with Adobe Reader and then printed out.

At the moment the PDF-Export just generate an PDF-File without form-fields.

If we open any VBA module (either a module or the one in code-behind-forms), one of the choices we have is pointing the Jet or Ace engine to the correct Reference Library. This dialog box is very small and should be bigger by default. Ideally it should be sizable and Access should remember the size where we left it. That would be NICE!

I support an application with over 90K registered users for a international logistics company (the guys with the brown trucks). We can not support the 64 bit version of Office Access because there is no 64 bit version of this library. Converting the Tree Views to use .Net would be cost prohibitive.

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.

When you are in the VBA Code Editor, and you want to refer to a field on the form, you have to flip back to the form to find the field name before you can use it.

It would life so much easier if the field names were listable in the code module in the View option as per the Object Command on the Form's Design View.

Create more than one PDF-File from the Report and merge the PDF-File to one PDF-File

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.

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.

When in tabbed View, it would be nice to be able to drag tabs to rearrange them

thank you

Please add the capability to call stored procedures in a remote ODBC database with DAO, like it existed in the past with ODBC-Direct-Workspaces.
Pass-Through-Queries are only a kludge because parameters have to be concatenated into the sql string.

Scenario: Product Obsolete.
if product is marked as obsolete then we do not want it to appear on the combo drop down list but still must be visible to display historic data.

The Hack involves hiding a second drop down behind the first with a different rowsource, on click of the first we swap focus to the rear dropdown which then retrieves the required value without effecting the bound tables historical data.

Can you apply a filter to a combo box, on focus, for addition of records.