I'd be interested what forumers thought about this.
http://forums.olapforums.com/viewtopic.php?f=5&t=637
I know it's a crosspost, but...
-
- Site Admin
- Posts: 1458
- Joined: Wed May 28, 2008 9:09 am
- jim wood
- Site Admin
- Posts: 3958
- Joined: Wed May 14, 2008 1:51 pm
- OLAP Product: TM1
- Version: PA 2.0.7
- Excel Version: Office 365
- Location: 37 East 18th Street New York
- Contact:
Re: I know it's a crosspost, but...
Not a suprise, you don't get a solid solution when you just bolt things together. Just ask out friends at Cognos....
Struggling through the quagmire of life to reach the other side of who knows where.
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
-
- Site Admin
- Posts: 6643
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2.0.9.18 Classic NO PAW!
- Excel Version: 2013 and Office 365
- Location: Sydney, Australia
- Contact:
Re: I know it's a crosspost, but...
What's PerformancePoint?David Usherwood wrote:I'd be interested what forumers thought about this.
http://forums.olapforums.com/viewtopic.php?f=5&t=637
(Kirkian to English translation: "Meh, who cares...")
It's probably of significance to the handful of poor sods who implemented the software. (Serves 'em right for not using TM1.

Does... not... often...abandon... WHERE has this guy been getting his mushrooms??It is less clear what will happen to any customers who have succeeded in deploying PerformancePoint Planning. The number cannot be large, but is probably greater than zero. There are also partners who have invested time and resources in PerformancePoint, whose efforts will turn out to have been wasted. Microsoft, which does not often abandon products in this embarrassing way, will need to do whatever it can to placate them.
I can think of a stack of VB6 developers who are feeling quite distinctly bent over. I can think of the volume of DAO code that needed to be rewritten into the latest "object model of the day" when MS stopped upgrading DAO, and which will in turn need to be rewritten again when THAT alphabet soup is replaced. I can think of the number of Access developers who relied on user level security and who got a seriously nasty surprise when Access 2007 came along.
Granted only the first of these involved the actual abandonment of a product. And granted MS denies even this, claiming that the camel that is VB.Net is really the same thing as the horse that was VB Classic ("Look, 4 legs, a nose, 2 ears, what more do you want?"), but in some quarters MS is getting a distinctly unsavoury reputation for hanging customers out to dry.
Still, I'm sure that PerformancePoint purchasers will be given an "upgrade wizard" to, oh, something or other, we'll figure that out later.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.