Could you please improve the handling of Unicode Latin Extended-D characters in MS Access queries and filters. Currently, chars in this range (introduced in Unicode 5.1 back in 2008) are incorrectly compared. Thus SELECT (ChrW(42786)=ChrW(42841)) AS Expr1; falsely returns a True value although two different chars are compared. The same is true for any two signs in this Unicode range. The problem only exists in Queries; in VBA Code these strings are compared correctly (except the StrComp function with vbDatabaseCompare option). See MSDN c76d9e5f-adbc-41f3-a2ed-dc25edf34a14

When using the vbYesNo message box you can only have 'Yes' or 'No' options. I would like to be able to rename these options. Currently the only way round it is to create a form to look like a message box.

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.

We should be able to generate reports as PDFs with a password. MS Word has an encryption option when saving a Word Doc to PDF.

For security reasons, more and more organizations want to have encrypted data at rest and in emails. ACCDBs support encryption, so it'd be helpful if it's PDF outputs could too.

It should be available from the user interface and as an option programmatically (DoCmd.OutputTo acFormatPDF).

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

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.

With comprehensive applications, it isn't hard to get the dreaded "Can't open any more databases" error message.

When this message is encountered, bad things happen internally and the database should be restarted.

If this isn't possible, at least give us a handle so we can determine the number the system currently thinks exist.

When building a system that shares its data with other systems - I've built an ERP system with Access - you often want to share certain Master data (from the HR system for example), but want to keep it that only HR can modify the data.
If we could set linked tables to be read only, that would remove the need for a lot of 'protectionist' coding.

Often the Datasheet heading is much longer than the values in the column under the heading. Making the column narrower (to see more columns) means I can no longer read the heading.

We are working with 32-bit add-ins for access. But it is not possible to work in 64 bit system which I am using.

When connecting to a commercial database such as Oracle, it may be trouble if all the columns of the table are not displayed.

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.

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.

When a query fails due to data type mismatch or some other field specific error - tell us what field in the error message.

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.