What happened to Pivot Table view in Access 2013?

Maybe I should have been more clear:

* Because a superior version exists in another MSFT tool (Excel) and maintaining both seems wasteful

* Because even maintaining a feature throughout the versions requires manpower which we like to pour into the web features

* Because data from the Customer Experience program tells us few people use it.

There are several other features cut from A2013 that fall in this category. I understand you don't like it, but there is a rationale, and there is a path forward.

The Excel pivot table is NOT superior to Access.  They do not operate the same way.  Access HAD the ability to filter data on multiple levels. That is what made it so powerful.   Crossing between systems is inefficient.  

Disappointed that neither MS or its MVP's understand this.  

Maybe I should be more clear:   Has Microsoft or its 'MVPs' actually used Access pivot tables?

I have heard rumors that Microsoft was worried that MS Access was too good, and would compete with a new Business Intelligence tool they are introducing.  The least they can do for developers is to offer the pivot table functionality as an add-in. 

The reason I heard was that they did not see any need to duplicate the feature in both Access and Excel, so they stripped it out of Access to "save money on development".  Sounds like a lame excuse to me, but there it is.  They also removed PowerPivot from consumer licenses because the BI group decided it is a "business feature". <sigh>

You can now send the feed back to the "UserVoice.com" sites. It appears that MS really is reviewing and acting on some (a very few) of the suggestions made on this site.

Here is the specific link you are looking for:

• Access -https://access.uservoice.com/

MS Suggestion box sites at "uservoice.com" Wiki

If you have an (other) feature suggestions to make for various MS products, here is a longer collection of MS uservoice.com sites:

**http://answers.microsoft.com/en-us/windows/wiki/windows\_10-desktop/ms-suggestion-box-sites-at-uservoicecom/7397119c-6d48-49e6-8d94-7bd0a50d214f?tm=1447217971960******

• http://office.uservoice.com/forums/285186-general - Office in general

• http://office.uservoice.com/forums/285186-general/suggestions/9906966-office-2016-quick-access-toolbar-too-wide 
• 2016 QAT is too Spaced OUT!

• https://office.uservoice.com/forums/285186-general/suggestions/10517283-allow-activation-without-the-need-of-a-ms-mail-acc
• don’t want Office 2016 tied to Userid

• https://office.uservoice.com/forums/285186-general/suggestions/10936428-visio-365-monthly-for-consumer-365-users-and-oth Visio 365 monthly specifically for Consumer licenses
• http://word.uservoice.com/ - Word
• http://word.uservoice.com/forums/304924-word-for-windows-desktop-application/suggestions/9253599-bring-back-classic-text-boundaries
• Recreate the single text margin around page like 2010 and earlier

I am an accountant and a system manager, and I have used MS Access for years as an office automation, report writing, and application development tool.  I depend on it and I use it every day to query and report from large business system databases.  The Pivot Table/Pivot chart functionality was one of the best and most useful enhancements ever made to Access, and I have created several applications that use it as a central feature.  Now I feel like Microsoft has pulled the rug out from under me as a developer.  Excel doesn't handle large number of records like Access, and my application is in Access, not Excel.

It blows my mind that Microsoft would pull this important functionality out of the app and take a giant step backward.    New releases are supposed to mean enhancements, not degradations. 

I have heard rumors that Microsoft was worried that MS Access was too good, and would compete with a new Business Intelligence tool they are introducing.  The least they can do for developers is to offer the pivot table functionality as an add-in. 

Please confirm for me what the reason was for pulling this important functionality, and please share this feedback with the Access development team. RESTORE PIVOT TABLE FUNCTIONALITY TO ACCESS!

You would have more feedback but where do I send it?  Now I am forced to stay on Access 2010 until we can convince you that pulling pivot table functionality was a mistake.

I took several years programing in access. Beginning with access 97 through to recently to pass at office 2010. About these years MS always has shown a bet to improve Access, and i enjoyed it.

Now I view sadly that one of the most powerful tools to give a Access a seriously appearance, to be disappeared as smoke in A 2013.

Why? Really MS what need to made it now?

I see the same solutions to this big bug (for me...), migrate it to Excel, so that implicate few problems.

First, not all final user have known how work with Excel. (connect to data base, decide whats field to database it contains the informations that are looking, then design..) Simply I think not is operative.

Second, if I have a database in access protected with password, really i have to give at all users the password to they can connect with the database? In Access 2010 it not was necessary to do it, only you need implement at pivot table with same fields and the users was being able to change it to they need made.

Well, I hope the development people of MS will keep in mind to the newest versions the possibility to made a... downgrade? (is strange say  it...) and apply again this great tool. Another way, I hardest think to migrate another platform to continue programing, and this is sad after so many years of efforts.

The removal of Pivot views from Tables and Queries is a problem.  Earlier samples issued by Microsoft strongly used this feature & now it's abandoned. 

Without poling the user community it's difficult to understand the impact this has, but I believe there's a lost opportunity aspect as well.  It was quite handy to quickly show the results without (a) developing a Chart in a form/report or exporting to Excel.

This was further useful when viewing linked tables to say an MS SQL database.