What happened to Pivot Table view in Access 2013?

I'm not here to fight with you. I'm just trying to correct inaccuracies. I never said that MS hasn't put in features that have been good for developers. I'm saying that most of those features came about as by products of something else. I've stated that Access was never designed specifically with the developer in mind. It was designed as an end user/small workgroup platform. And I stand by that statement.

SSMA was developed by the SQL Server team not the Access team. Pivot tables were developed by the Excel team. You have to understand that MS product development teams don't work together as well as we might like. 

And ULS is still available if you want to use mdb files.

So Scott please correct my reading of you here. When Microsoft designed the Access runtime version, the security model, the ADP option, the upsizing wizard etc. They never had any developer in mind? These features were meant for end users but were just inadvertently used by developers, is that it?

How is it net gain to be forced to download and use another program to migrate tables to SQL Server? A net gain would have been if SSMA had been integrated into Access. You might as well argue that removing Pivot Tables is a net gain too. After all, all Access users will have Excel too.

Nobody is arguing that JET is as good as SQL Server but for small businesses and single user systems it might well be adequate. Since 2003 though you cannot implement a simple JET solution with any security.

Why do you think ADP was a flawed attempt at moving from JET to SQL?

The only way it becomes a contradiction is if you don't read what I actually have said instead of what you want to think I said. That Access is  a tool for a small business developer is undeniable. That doesn't mean that Microsoft planned it that way, Yes, Access was designed from the beginning to be an end user/small workgroup tool. That it has become what it has is mostly inadvertent, not planned.

And no, those things don't support your argument. Migration to SQL Server was improved with SSMA so the Upsizing wizard became unnecessary. Net Gain! Pivot tables are a net loss, but the ability to do Pivot tables was not taken away just moved. Granted it makes doing them more cumbersome, but its not a complete loss. As for the security feature, MS is moving away from Jet and towards SQL Server, has been for a while. ADPs were a flawed attempt at that, SQL Server clearly has a much more powerful security model. It was removed for the same reason other features were removed. MS has a limited amount of resources and has to prioritize what it can support. I don't understand how you can say that is not consistent with Access as a Developer platform. Doing so shows a lack of understanding of what Access is. The Jet engine is just one part  of Access. It is actually it's weakest part. But the fact is that it is an interchangeable part. One can develop a full application in Access with UI, reporting and workflow processing and then plug in almost any database engine.

ADP was not an alternative to ODBC it was an alternative to having a full JET based front end. Why remove the option unless it was to reduce developer options? What you describe as "quirky" with disdain was actually a pretty handy feature. Now, if you want to secure an Access database you have to upsize to SQL Server. Again... not consistent with Microsoft promoting Access as a developer platform.

You seem to be contradicting yourself, Scott. You say you doubt Microsoft ever were interested in the small-time business developer in one sentence and then in the next assure everyone that Access still is such a tool. In previous posts you've claimed Microsoft only ever intended it as an end user product.

There has been a net loss of developer features in the box since 2003. Sharepoint integration is poor and, in any case merely confirms my opinion that they are moving in an IBMesque way. Data macros are the exception but the loss of the security feature, pivot tables, and even the upsizing wizard supports my argument.