What happened to Pivot Table view in Access 2013?

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?

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.

Hi Scott. I'm glad you're not looking for a fight. Me neither. 

I think the point of contention is what constitutes an "inaccuracy". You have your opinion and I have mine. The fact remains that Microsoft designed a number of features into Access (e.g. runtime, security model, ADP, upsizing wizard, pivot table etc) that are pretty obviously aimed at developers and not end users. 

I am not sure why anyone would have an agenda to try to dispute that but you seem to be such a person.

Please tell me more about ULS.

No I'm not disputing that, what I am saying is that the primary focus of Access has always been the end user or small workgroup. That the primary focus has never been developers. Most of the developer features have arisen to give knowledge workers the ability to create apps that a workgroup can use. It was never the intention to create a dbase/Foxpro platform. MS already had FoxPro for that level.

This is a fact that I have learned from being involved in the Access community for many years and having many discussion with people from Microsoft who were involved in the growth and development of Access. So anyone who believes that Access was ever designed as a tool for developers is ignorant of these facts. 

ULS is User Level Security. It's the security model you refer to. It was deprecated from the 2007 and later file format, but its still there if you want to use the mdb format.

Primary focus maybe not but its a moot point when so many developers like me jumped on board. It had significant features for developers comparable with the xBase competition. 

Yeah, Microsoft acquired FoxPro and look what they did to that.

Your "facts" are just second hand opinions, ones you have no doubt filtered through you own beliefs. 

The salient facts here are that Microsoft designed the database product with a significant number of features that could only have been aimed at developers. Why deny it?