The Problem (Q-score 4, ranked #222nd of 303 in the Excel VBA archive)
The scenario as originally posted in 2013
This is probably a closable question, but really I think Stackoverflow is the best source where a practical answer can be found.
I’m working on a web page showing a pivot table. My solution is based on pure jQuery+html. Works pretty nice till now although some css work is still needed.
Anyway my project leader is asking me to try to host the excel pivot table connecting to analisys services as an object into the browser.
I don’t like too much that solution, but I need to have some more points than just saying is an out of date architecture.
The first point that come to me is that it only works in IE, but unfortunately the end customer is not just happy with that but also requiring IE.
Another interesting point is that the protocol who that funny beast would probably use to communicate with the server is something not really HTTP, just to make firewall happy.
End customer ( yes, the one who says IE is a requirement ) would eventually want to see the app working on IPad too, even if the project seems to stand sometime in developement, I doubt this time would be enough to Apple to properly port the ActiveX object in Safari.
What about? Are moi reason pointless, any more reason you see?
Why community consensus is tight on this one
Across 303 Excel VBA entries in the archive, the accepted answer here holds niche answer (below median) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — niche answer (below median) (+9)
Verbal answer — walkthrough without a code block
Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Excel VBA entries ranked in the top 10 of the same archive.
Enterprise decisions are driven by data and infrastructure, not code.
-
If all your customer’s data is stored in Analysis services, then all your JQuery+CSS wizardry doesn’t matter if they’re not able to pivot the data that they want
-
The custom protocol of Analysis Services is designed to pivot billions of records, your JQuery/CSS may not be that scalable yet
-
Most enterprises have only IE6/7 infrastructure, they don’t even have Firefox, let alone Chrome. They want you to support IE rather than upgrading every desktop
-
Customers who stress for IE compatibility hardly get around to supporting iPads in their infrastructure. Think Agile. Worry about things when they come, and don’t waste effort on skeptical/fictional things. My favorite quote here as a programmer is:
We design architecture and frameworks which support a thousand future possibilities. The customer somehow manages to come up with the thousand-and-oneth thing that we never designed for. Surely, they must be cleverer than us?
So you need to have an open mind on what you’ve been asked to do.
I’m sorry if this post doesn’t directly answer your question. But I want to leave it this way.
When to Use It — classic (2013–2016)
Ranked #222nd in its category — specialized fit
This pattern sits in the 97% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Excel VBA archive for a higher-consensus alternative.
What changed between 2013 and 2026
The answer is 13 years old. The Excel VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.