T
Teo Lachev
Is MS working on a new version of OWC which will support the new Analysis
Services features in SQL Server 2005?
Services features in SQL Server 2005?
A
Alvin Bruney [MVP]
owc12 is scheduled for the longhorn time frame. no idea what will be in it
or what it will support
or what it will support
T
Teo Lachev
Thanks for feedback, Alvin.
Alvin Bruney said:
T
Teo Lachev
I am hearing rumors that OWC is not going to be the vehicle for the BI
enhancements in the next version of Office. This makes me confused about the
future of OWC. Is it going to be replaced by another Office component?
enhancements in the next version of Office. This makes me confused about the
future of OWC. Is it going to be replaced by another Office component?
Teo Lachev said:
A
Alvin Bruney [MVP]
what is BI?
I haven't heard anything. (not that i am in the loop either)
--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
I haven't heard anything. (not that i am in the loop either)
--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
Teo Lachev said:
T
Teo Lachev
Alvin,
Thanks for your reply. BI stands for Business Intelligence. I heard that OWC
will be deprecated in a long run from Microsoft on the beta 2 OLAP forum. I
was re-directed for more information to the Office newsgroups.
To re-phrase my question. What is the long-term MS strategy for a smart
client for Analysis Services? It looks like MS tools are popping up like
daisies almost every month: OWC, Excel add-ins, Scorecard Accelerator, Data
Analyzer. This is confusing. I wish there was a single tool that does it all
which ideally could be easily integrated with .NET applications.
Teo
-----------
Thanks for your reply. BI stands for Business Intelligence. I heard that OWC
will be deprecated in a long run from Microsoft on the beta 2 OLAP forum. I
was re-directed for more information to the Office newsgroups.
To re-phrase my question. What is the long-term MS strategy for a smart
client for Analysis Services? It looks like MS tools are popping up like
daisies almost every month: OWC, Excel add-ins, Scorecard Accelerator, Data
Analyzer. This is confusing. I wish there was a single tool that does it all
which ideally could be easily integrated with .NET applications.
Teo
-----------
Alvin Bruney said:
A
Alvin Bruney [MVP]
Microsoft is pretty silent on the issue. Not that they would come out and
confirm or deny it anyway.
My opinion?:
OWC either needs to be written to be compliant with .NET or done away with.
The rewrite is not only because .NET is the new kid on the block, there are
several issues with performance and stability with
the components. The architecture is stretched and old and needs a rewrite to
get around those issues.
There is also the licensing issue and the components stepping on the office
suite of products shoes.
which way will it go? well, there is a strong business need for the
functionality provided by the OWC. If it is to be deprecated,
something else has to take its place to fill the business need.
Finally, Longhorn is imposing change on practically everything in a
radically different way. Either there is a newer and better way of providing
the functionality, or there is to be re-architecture of the components. The
one constant is that the components cannot continue to exist based on the
current architectural platform. I'd expect OLAP as well to undergo some
radical changes as well because it doesn't integrate seamlessly with .NET.
Also, bear in mind that if they decide to yank the product, it won't be the
first time that MS has jumped ship. It certainly won't be the last.
--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
confirm or deny it anyway.
My opinion?:
OWC either needs to be written to be compliant with .NET or done away with.
The rewrite is not only because .NET is the new kid on the block, there are
several issues with performance and stability with
the components. The architecture is stretched and old and needs a rewrite to
get around those issues.
There is also the licensing issue and the components stepping on the office
suite of products shoes.
which way will it go? well, there is a strong business need for the
functionality provided by the OWC. If it is to be deprecated,
something else has to take its place to fill the business need.
Finally, Longhorn is imposing change on practically everything in a
radically different way. Either there is a newer and better way of providing
the functionality, or there is to be re-architecture of the components. The
one constant is that the components cannot continue to exist based on the
current architectural platform. I'd expect OLAP as well to undergo some
radical changes as well because it doesn't integrate seamlessly with .NET.
Also, bear in mind that if they decide to yank the product, it won't be the
first time that MS has jumped ship. It certainly won't be the last.
--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
Teo Lachev said:
T
Teo Lachev
Alvin,
I completely agree. I grew to love OWC also. It is a marvelous piece of
technology. We had several successful WinForm and ASP.NET OLAP applications
running OWC.
I wish I could see OWC re-written to .NET instead of having to use Excel
add-ins
-
I completely agree. I grew to love OWC also. It is a marvelous piece of
technology. We had several successful WinForm and ASP.NET OLAP applications
running OWC.
I wish I could see OWC re-written to .NET instead of having to use Excel
add-ins
-
Alvin Bruney said:
A
Alvin Bruney [MVP]
And i think it will be. I suspect it will take a couple years of work though
which is why i was thinking longhorn time frame. remember the owc was
released in owc 9 which means versions 1 thru 8 weren't production ready. so
i don't assume that it is *easy to whip out a .NET version.
--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
which is why i was thinking longhorn time frame. remember the owc was
released in owc 9 which means versions 1 thru 8 weren't production ready. so
i don't assume that it is *easy to whip out a .NET version.
--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
Teo Lachev said:Alvin,
I completely agree. I grew to love OWC also. It is a marvelous piece of
technology. We had several successful WinForm and ASP.NET OLAP
applications
running OWC.
I wish I could see OWC re-written to .NET instead of having to use Excel
add-ins
-
Alvin Bruney said: