After all my evangelizing (or complaining if you like), I think it's important to acknowledge when someone does/announces something that addresses my concerns.
Post titles are the first things that come up in search engines. So if someone is searching on the question "Will PowerPivot support VBA", they're likely to see my last post come up in a search engine. That post holds a critical comment from Amir Netz of the PowerPivot team at Microsoft, and I don't think it's really fair to have it publicly advertised under the heading that is completely opposite of the truth.
So this post is short and has only two purposes:
- To admit I was off base in some of my comments (and I've never been happier to admit it!)
- To get something into the blogosphere to answer this burning question with factual information.
To recap, Amir's comment:
PowerPivot does not have VBA support for the most simple reason: we just did not get to it yet.
We know how much you want and need it. We have it high on our list and you will get it. But it is a big deliverable that requires time to complete.
So there you have it. PowerPivot will get VBA. Not quite yet, but it's comingâ€¦ the only question is time.
You can read the full post here.
The text passage is a blog post that addresses a previous critical comment about PowerPivot's lack of VBA support and updates the audience on the status of VBA support in PowerPivot.
no_question
- the passage does not contain a mathematical question or any form of calculation. it is primarily an update on the development status of a software feature.
Given a text passage, determine:
    1. If it contains a mathematical question (including word problems or calculations)
    2. If an answer to that mathematical question is provided in the text

First, describe the content structure you found in 1-2 sentences.

Then provide your analysis in the following format:
TYPE: <one of the following values>
- NO_QUESTION
- SINGLE_QUESTION
- SINGLE_QUESTION_WITH_ANSWER
- MULTIPLE_QUESTIONS
- MULTIPLE_QUESTIONS_WITH_ANSWERS
system
After all my evangelizing (or complaining if you like), I think it's important to acknowledge when someone does/announces something that addresses my concerns.
Post titles are the first things that come up in search engines. So if someone is searching on the question "Will PowerPivot support VBA", they're likely to see my last post come up in a search engine. That post holds a critical comment from Amir Netz of the PowerPivot team at Microsoft, and I don't think it's really fair to have it publicly advertised under the heading that is completely opposite of the truth.
So this post is short and has only two purposes:
- To admit I was off base in some of my comments (and I've never been happier to admit it!)
- To get something into the blogosphere to answer this burning question with factual information.
To recap, Amir's comment:
PowerPivot does not have VBA support for the most simple reason: we just did not get to it yet.
We know how much you want and need it. We have it high on our list and you will get it. But it is a big deliverable that requires time to complete.
So there you have it. PowerPivot will get VBA. Not quite yet, but it's comingâ€¦ the only question is time.
You can read the full post here.
user
The text passage is a blog post that addresses a previous critical comment about PowerPivot's lack of VBA support and updates the audience on the status of VBA support in PowerPivot.

TYPE: NO_QUESTION
- The passage does not contain a mathematical question or any form of calculation. It is primarily an update on the development status of a software feature.