Feedback by UserVoice

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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. MS Access on MAC

    At this moment I'm a subscriber of Office 365, but always I worked with Ms Access. Now, I have a Mac book Pro and is not possible install it. I also work with other tools, like Excel, but I would like to see the MS Access to be compatible with IOS system, because it's a wonderful tool, and I can't have both systems (Windows and Mac).

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Queries  ·  Flag idea as inappropriate…  ·  Admin →
  2. Please restore the Pivot Tables to MS Access 2013

    Many people in my off use the pivot tables that I produced in MS Access, since the change they are now just useless datasheets. I can not expect the staff in the office to export the data and convert it to pivot tables in MS Excel. Please return this feature ASAP. Thanks

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We realize that Pivot Tables and Charts have been a great feature and many Access users found them to be highly useful.
    As you may already know, they have been removed as the technology they relied on, was no longer supported (Office Web Components).

    At this point we have no plan to bring Pivot Tables and Charts back. However we are looking into ways to improve and modernize data visualization in Access.

    Stay tuned.

  3. 166 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    40 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We realize that Pivot Tables and Charts have been a great feature and many Access users found them to be highly useful.
    As you may already know, they have been removed as the technology they relied on, was no longer supported (Office Web Components).

    At this point we have no plan to bring Pivot Tables and Charts back. However we are looking into ways to improve and modernize data visualization in Access.

    Stay tuned.

  4. In some Access export commands path length is limited. Could you remove those limitations?

    In some Access export commands path length is limited. Could you remove those limitations?

    ' works:
    
    DoCmd.TransferSpreadsheet acExport, acSpreadsheetTypeExcel12Xml, "Mitarbeiter", "C:\Users\Gerrit.Viehmann\Desktop\Very looooooooooooooooooooooooooooong directory\Very loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong filename.xlsx"
    ' Error 2006:
    DoCmd.TransferText TransferType:=acExportMerge, TableName:="Mitarbeiter", FileName:="C:\Users\Gerrit.Viehmann\Desktop\Very looooooooooooooooooooooooooooong directory\Very loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong filename.txt"
    ' works. Add one ‘o’ and it doesn’t:
    DoCmd.TransferText TransferType:=acExportMerge, TableName:="Mitarbeiter", FileName:="C:\Users\Gerrit.Viehmann\Desktop\Very looooooooooooooooooooooooooooooooooooooooooong filename.txt"

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Automating Tasks  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for posting.
    The limitation in this case is on the filename itself, not the path. For file types, the database engine treats the file name as the table name in an external data source, so it enforces the limit on table name length, which is 64 characters.
    At this point we have no plan of changing such a fundamental behavior in Access.

  5. HURRY UP AND MAKE ACCESS ON MAC!!!!!

    Mac needs an amazing database software and time and time again, you still don't create a version for Mac! MS Remote Desktop is not ideal when you need to use Access all the time! Look at everyone on Mac that is suffering. JUST MAKE A MAC VERSION.

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Restore Pivot Tables to Access!

    I work at a major US airline. I have been charged with creating major database work using MS Access. Pivot tables are vital to the amount of varied data with which we work. Pivot tables are vital...please restore.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. VBA Break or Cancel ability in debug mode

    In testing a vba fuction that is running badly or seemingly endlessly, I used to be able to press CTL+Break to stop it from running. In Access 10 this no longer works, I have to completely crash out of Access - which i hate to do with a huge db. There should be a way to cancel safely?

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Collapsible vba procedures

    By default each procedure should only have the first procedure line (header) visible with an expand button to show all lines within the procedure. Currently a lot of time is spend scrolling through code.

    I would also like to see the two drop downs for general and declarations changed to a tree view on the left so that I can more easily navigate procedures and methods.

    Thanks for your consideration!

    48 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add Pivot Charts back to Access.

    The original Pivot tables and Pivot Charts in Access 2007 were very easy to use and a great benefit to builders and users. I am still using 2007 for that very reason, since I have many applications that rely on the pivot functionality and I am a great believer in graphical representation using Pivot Charts.

    696 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    121 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks everyone for voting and supporting this suggestion.
    As you are all aware, Pivot Charts and Pivot Tables have been removed from Access 2013 because the technology they relied on was deprecated (Office Web Components).

    Voting and commenting on this suggestion (and on this https://access.uservoice.com/forums/319956-access-desktop-application/suggestions/11510094-put-pivot-tables-back-into-access-surely-a-databa) has been very valuable to us to distill the requirements and needs.

    Since Pivot Charts as we all know them, will not come back to Access, we are updating the status accordingly and would like to encourage you to continue and use your free votes to support other suggestions.

    Thanks,
    Michal [MSFT]

  10. Put Pivot Tables back into Access. Surely a database should be able to analyse data, including text fields. This cannot be done in Excel.

    Put Pivot Tables back into Access. Surely a database should be able to analyse data, including text fields. This cannot be done in Excel which can only handle numeric data. Our business uses them extensively and currently we cannot find an alternative.

    324 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    32 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Undo in VBA editor

    VBA editor allows to undo only the last 20 steps. That feels like programming in 1984. I don't think there is any reason not to raise this number.

    60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Reports  ·  Flag idea as inappropriate…  ·  Admin →
  13. Ribbon Creation Tool

    You pushed upon the Office community the Ribbon back in 2007, when are you going to finally give us a GUI tool to develop ribbons properly? Right now, the ribbon is a half-baked concept with no tool to develop with.

    162 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    29 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →

    At the moment there is no plan to develop a tool for creating ribbons.
    This suggestion should probably be directed to a broader UserVoice site as it relates to all Office products and not just Access.

    Thanks,
    Michal [MSFT]

  14. Put the ADP file option back into Access 2013 and beyond...

    ADP's provide a simple connection to SQL server. In addition, Forms and reports have properties that simplify retrieving data.

    95 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    No Current Plan  ·  19 comments  ·  External Data Connectivity  ·  Flag idea as inappropriate…  ·  Admin →
  15. Provide a native grid control similar to the visual studio gridview or even the old flexgrid.

    A grid control provides the means to show tabular data. Some features include
    - Sorting by column
    - Moving columns by dragging
    - Selecting individual cells
    - Formatting individual row, columns, or cells
    - Control columns such as checkboxes for selecting a row
    - Edit cell of data
    - Spreadsheet type movement

    The capabilities provided by the Visual Studio gridview is a great example. The features that this provides are far beyond what is capable in Access especially when dealing with unbound data. A common example that I see on the message boards is a user want to build a…

    303 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    No Current Plan  ·  12 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Access for Apple PC's

    Can we have a version of Access that will work on Macs. As a developer, it is a real turn-off when I have to tell people that the only way they can use an Access Database is via the Web or via Remote Access.

    Access could then claim to be a universal database.

    72 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Stop randomly omitting text in reports

    Sometimes, MS Access reports silently omit lines of text. This bug exists since at least Access 2007, and it's very annoying -- customers have to manually double-check every invoice to make sure that everything important has actually been printed.

    The bug is well-known (see, for example, StackOverflow questions 10612364 and 14716048, SuperUser question 455782, MSDN thread 648dd3a2-28c1-4f0d-853c-ef932c58519f, or Microsoft Support Cases 114032111284860 and 115072312971316), but, apparently, has not been considered important enough to be fixed.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for reporting.
    We will add this bug report to our backlog and see that it is prioritized and handled.
    In the meantime, I’m updating the status for ‘No Current Plan’ so that you use your votes again.

    Thanks,
    Michal [MSFT]

  18. Enable multiple versions of Access to co-exist on the same machine.

    Enable multiple versions of Access to co-exist, side by side, on the same machine without ill effects.
    Just like there can be multiple versions of Visual Studio, SQL Server, etc. Currently, to work in different versions of Access we need to maintain a separate machine (physical or virtual) for each version of Access.

    82 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Alphonse,
    It is not clear what is the problem you are encountering. Going through the comments other Access users left here, didn’t help figure it out as well.
    To the best of my knowledge there shouldn’t be an issue with running multiple versions of Access on the same machine, so I’m closing this request.
    If you feel strongly about it and can provide more information, please create a new request.

    Thanks,
    Michal [MSFT]

  19. Give the VBA IDE a major overhaul finally

    It's been over 20 years since the VBA IDE was created in its present form. MS has since created a number of modern and efficient development environments. Even if the VBA environment has long been referred to as outdated: it is simply the everyday reality for all serious Access developers (to a lesser extent this is also true for the other Office programs). I can not imagine that it lacks capacity to MS to bring the VBA IDE into a more contemporary form.

    To insist that it would not be worthwhile to invest in an improved IDE, is roughly as…

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Bring back the Database Window

    The Nav Pain is thoroughly unsuitable as a UI for very large, well-established projects. Small, user-created files with 10's of objects are suitable for the Nav Pane, but large, professionally developed files with thousands of objects are most certainly not. The Nav Pane lacks the visual differentiation to make finding objects simple -- and no, search is not a substitute for a good visually-oriented UI design.
    The Nav Pane is a drag on developer productivity

    71 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We have heard from customers who have been using the database window for a long time that they would like us to bring it back, as it is superior to the Nav Pane.

    At this point we have no current plan to bring it back.

    However, if you have specific suggestions on how to improve the Nav Pane, please submit them as separate items.

    Thanks,
    Access Team

  • Don't see your idea?

Access (Desktop Application)

Categories

Feedback and Knowledge Base