H
Harlan Grove
Access, SQL Server, OLAP, MDX and VB.Net.. oh gosh.. where do we start? ....
it is a revolution that happened 4 years ago.. and somehow beancounters were
left out.
A very quiet revolution indeed.
I'm unimpressed in part because I work for a global financial services
company that uses OLAP via Essbase via browser interface. It may suck
compared to what you're espousing, but Essbase was out there *before*
Microsoft, as was Applix with TM/1. Those are the only two OLAP products
I've used. There may be others. The point is that companies bought these
other products and used them to develop applications of modest to
considerable value for their companies. There are *working* systems using
these products, so most sensible IT managers aren't going to switch to
MSFT's offerings any time soon. That's good business even if if did make for
boring development.
It is all the same product.
Really? As in buy one (Access, say), get them all? More foolishness!
OLAP is magical.. if you haven't used it (similiar to cognos, etc) then
you are really short-changing yourself.
I used (as a developer of sorts) the 'multidimensional database' in
VP-Planner back in the 1980s and TM/1 in the early 1990s. I've had access to
browser-based Essbase applications. I know how the first two worked, and I
can make reasonable guesses about the third. They have their uses, but they
don't do much for me in what I do.
MDX is going to change the spreadsheet community.. and I hope for the best
of all of you-- that you spend some time and energy in broadening your
horizons..
No it won't, at least not soon.
People who misuse spreadsheets to produce reports involving few calculations
(my definition) but lots of in-house data available via ODBC or other
electronic sources will likely continue to do so as long as (1) it isn't too
slow (up to them and their bosses to measure that) using spreadsheets to do
so and (2) spreadsheets are the only GUI development tool they have (writing
& running .VBS or .WSH files doesn't count as GUI development to me, though
most people running recent Windows versions have this option too).
Then there's all the other uses of spreadsheets which you can't comprehend.
Resorting to metaphors, you're arguing that pickups with back seats are so
damn useful and capable they'll replace all other types of private passenger
car. Not in this lifetime or the next.
....MDX has what-- 80% of the functionality of Excel ... times the power of SQL
Server?
The 80% may be correct, but the key question is which 20% would it be
missing? If it's a critical 20%, it won't do squat to replace Excel. Also,
if it costs more per seat than Excel, it won't do squat. Finally, if it
requires a network connection to do anything useful, Excel will continue to
thrive.
....Microsoft needs to start offering a variety of tools-- like soemthing that
would help developers to translate between VB6 and VBscript.
If you knew C, you could roll your own compiler from one to the other. In
the same way that the GNU FORTRAN compiler compiles FORTRAN code to C rather
than to object code. You just gotta know how to use a lexical analyzer and a
write a parser grammar.