Access (Desktop Application)
Welcome to the Access Desktop feedback forum! This is the place for users to send us suggestions and ideas on how to improve.
We have partnered with UserVoice, a third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.
-
4 votes
-
Allow Object Model Manipulation of the ctl.Filter.ValueList.RowSource in a Form Datasheet
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.
1 vote -
Fix the TransferDatabase command so that it exports tables to Oracle properly.
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.
5 votes -
Create an "expert mode" option that disables Access novice features in design mode.
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.
14 votes -
Report Events Need To Be Cleaned Up
You really need to clean up the Report Event Model so that code inside a Report gets fired the same way in Preview, Report and Print modes. It is obvious from the Internet that lots of people have run into this and there is little or no common-sense help on this issue ... this itself is strange.
If, for example, you add a message box in the OnOpen Event of a report, the message box fires if you run Docmd.OpenReport with the acViewPreview switch but not if you use the acViewPrint or acViewReport switches.
If you place the same code…
6 votes -
Create an "Access Enterprise" version with most of the improvements we've suggested.
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.
10 votes -
Provide an easy way to share Rich text between Access and other Office Applications
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.
33 votes -
Add Save As... back to the Query context menu
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.
20 votes -
Have "native english" Naviagation pane - even if using LanguagePack (like german)
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.
2 votes -
non editable System Queries For Listbox etc.
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.
3 votes -
Combox - separate what is shown when "open" to what is shown when "closed"
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; ) ...
4 votes -
Add a .Workspace property to the DATABASE object. Also, add Properties to the WORKSPACE to reflect whether any TRANSACTTIONS are open.
There is currently no pointer from an open Database handle to point back to the Workspace it is a part of. There should be - we get away with this because Workspaces(0)(0) is the detault 99.999% of the time. However, what if it isn't? We can't tell form looking at the open database handle, and that's actually pa problem, especially if one needs to react, say in a bit of generic error handling code, to any pending/open/hanging TRANSACTIONS in the relevant WORKSPACE.
Which brings me to the second point - there is no available STATUS properties of the DBEngine, Workspace,…
5 votes -
Attach SQL tables without "dbo_" or give the option to do so
It would be more intuitive to link sql tables WITHOUT the owner prefix.
11 votes -
wpf
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 databases12 votes -
java
Java Driver
please create a driver for java, so that it would be able to create a android frontend to accdb-databases3 votes -
Highlightable property for all controls including rows on continuous forms
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.
3 votes -
Fix saving column order in datasheet view
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.
90 votesNote that typically the reason this happens is that there is code behind the datasheet form that modifies properties on the form or controls (e.g. Textbox.Locked). Access intends to save the datasheet column widths without saving the properties changed in code, and that process was not working as expected. We are planning to fix this, but in the meantime, you may be able to work around this if you can avoid changing form/control properties in code (e.g. by using Conditional Formatting instead)
-
Create error log file for all messages but it must include enough audit info
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.
13 votes -
Additional Error Object properties - which procedure, which module, which object, which db
The error object should be expanded to included properties which can reveal the procedure, module, and object that the error is taking place in.
0 votes -
USysNotes Object for documentation
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.
27 votes
- Don't see your idea?