Feedback by UserVoice

I suggest you ...

Add PowerQuery to ACCESS

PowerQuery is the best improvement for collecting data for Excel since many years. I would love to use it in Access too, without using Excel.
I would like to extract data from SAP, WEB, CSV-Files, collect all files from a folder, de-pivot files... Any ETL job PowerQuery supplies für Excel, but directly in Access!
(I posted this two years ago using other words)

630 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Peter Rühm shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
No Current Plan  ·  AdminAccess Team (Product Manager, Microsoft) responded  · 

PowerQuery is a great Excel feature which allows users to discover, combine and refine data across a wide variety of sources.
Access allows users to connect to a wide array of external data sources in a way that is unique to Access users and scenarios.
When we think of data management solutions across Office, we think of Excel and Access as somewhat complementary products, but not competing.
With that, duplicating capabilities from one product to another is not supportive of this perspective.
We are looking at further enhancing and improving Access’s abilities to connect to external data sources, but not in the form of integrating PowerQuery.


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Charley Kyd commented  ·   ·  Flag as inappropriate

    In Office 2016, Microsoft offers no practical way to set up hub-and-spoke reporting of many megabytes of data from many sources. Instead, each workbook must use Power Pivot to download, clean, and manage duplicate data from the original source. (At least, we hope that data we INTEND to be duplicated actually IS duplicated across the company in hundreds of workbooks!)

    Power Query can't READ data from a Power Pivot Data Model. And therefore, Excel users have no "one source of truth" within Office 2016.

    That design encourages users to connect Excel to a "real" database, which Microsoft will be happy to sell to us.

    I wouldn't plan on Access ever having Power Query. If it did, Excel users could treat an Access database as their one source of truth, which would give us a fairly powerful, Office-only, hub-and-spoke design.

    In other words, Microsoft isn't worried about Access and Excel competing; it's worried about Access competing with their "real"—that is, non-Office database products.

  • Peter Rühm commented  ·   ·  Flag as inappropriate

    I still do thoroughly hope, you will integrate ETL-features to Access!
    In EXCEL as well as in PowerBI you can use "retrieve and transform data" to collect data from diffent sources.
    I don't want to write back data to the sources.
    Many of my clients - financial controllers and data analysts - use ACCESS as a kind of datamart for their reporting, as I wrote in my BLOG "controllingexcellent". They collect data from different source, mostly TXT-files, CSV, Web, EXCEL-Files and Databases at the same time.
    It is the "single source of truth" where data is stored. Many other reports in EXCEL or PowerBi receive data from this single source, where all data has the same relevance.
    Here it is also possible to update just part of the data, without re-loading those parts loaded previously. Timestands help to control the topicality of the updates.

    I don't see any competion between EXCEL an ACCESS, I think each should be used, for what it does best. ACCESS stores data.

  • Dan Moorehead — PowerAccess commented  ·   ·  Flag as inappropriate

    With Power Query integrated into Power BI now, like Excel, I agree it should be extended to Microsoft Access.

    It's for that reason I'd developed PowerAccess ( and PowerSQL (as well as PowerGit) to extend MS Access with 500+ new PowerQuery-like functions (as well as Finance, BI, Analytics, Reporting & Excel functions) for use in SQL, VBA and Query Designer.
    PowerAccess and PowerSQL also extend Access with support for fast, intuitive XPrevRow()-based Excel-like formulas for queries.

    I developed PowerSQL for MS Access to provide not only Power Query-like functionality in Access, but also to enable Excel to Access conversion, even for financial / analytical models which require truly iterative calculation (for forecasting, projections etc) when otherwise impossible in Access, and yet so easy to do in Excel.

    These new Access features are provided together with new tools, like Global Find & Replace (across all SQL / Queries / VBA / Records / Macros, etc.), PowerGit (for automated, Git versioning of VBA, objects and data in Access / Excel / Office), Calculated Tables, and VBA CodeGen, Table / Data Macro auto-generation, user/row-level security, user edit/view restrictions, record edit rollback/undo/compare, cloud sync.

    Also, PowerAccess.NET provides VSTO-like .NET API for MS Access (version-independent) Add-in development and Automation in C# and VB.NET.

    And PowerAccess enables accelerated Excel to Access (formulas to SQL queries) conversion, automated Access to SQL Server / Azure backend automated/accelerated conversion.

    These (and many other) new tools & features are provided to modernize and automate use of Microsoft Access by experts, as well as simplify and enable use by anyone familiar with Excel.

    I appreciate the attention the Microsoft Access team has given of late to user suggestions, integrating charts, big int and other new features, and bringing Access to nearly all Office editions. And I would suggest integrating support for Power Query, adding back Access support to Visual Studio Tools for Office (VSTO) directly, as well as many other enhancements (like built-in Global Find & Replace, SQL syntax highlighting/preserved formatting/auto-complete, etc.).

    However, in the mean time, you may find PowerAccess, PowerSQL, PowerGit, and PowerAccess.NET a usable workaround to enable these kinds of much-needed features in Microsoft Access.

  • isladogs commented  ·   ·  Flag as inappropriate

    Whilst I'm grateful that MS have finally responded this is completely missing the point.

    There are many features that both Access and Excel have now e.g. charting, importing xml and of course vba. Access used to have pivot charts which were removed several years ago. Their removal certainly didn't help Access users. Adding Power Query to Access would not be unnecessary duplication as the 2 programs are not interchangeable. 685 votes is a clear indication that a lot of users would find this feature useful. Certainly far more useful than some of the recent improvements to Access that relatively few had asked for. If this user voice forum means anything, MS would act on features that are requested repeatedly.
    Still I will thank you for leaving a gap in the market for which I have an app for sale - JSON Analyse and Transform for Access (JATFA). Blatant plug!

  • Karl Donaubauer commented  ·   ·  Flag as inappropriate

    For many years Access was marketed as "Landing platform for data". Today it is far behind concerning modern data sources. It is nice but doesn't give the product a boost to bring back old dbase support or to add a few new data sources _exclusively_ for the 2-3 more expensive O365 plans. Don't tinker, think big! ;-)
    The complete Access product family, i.e. all users, needs a broad range of interfaces to modern data sources. It is PowerQuery that does this job (+ many useful transformations) for even older Excel but also for modern PowerBI etc.
    Therefore Microsoft should do an in-depth consideration and discussion to integrate PQ with Access, catch up a 15 years in data source integration and add a feature set that really has an impact to our practical work and is noticed by millions of Access users.

← Previous 1 3

Feedback and Knowledge Base