Note quite ! I still believe that there are 10 types of people in the world - users 
and developers !

So YOU, as a developer, would construct a cube with the 6 "key" fields that the user 
is interested in. You also get to do things like define an "opening" view of the 
information - AND also the query that is used to generate the cube (BTW, did I mention 
that Visage has a drag'n'drop query facility :-)

A single cube design can be used with multiple queries - you save each of these as a 
combination, which REALLY defines the cube - so you don't have to "remember" your 

Neither you, nor the user, need to worry about "format" statements, as this 
information will come directly from your dictionary (though there is an API that you 
can use if your database does "naughty" [with the benefit of historical hindsight] 

Just as each of your existing reports was stored as a "program" which you only wrote 
once (and modified/enhanced many times!), so with a data warehouse product (any/all of 
them) you only have to define these things once, and you can make enhancements as 

Obviously YMMV, and OLAP/DW/BI cubes will not solve EVERY problem - but our experience 
has been that they can certainly greatly enhance the user experience with what happens 
next !

(If you are interested, point your browser @, download the whitepaper & 
then "play" with the live demo. Left click on the "Department" at the top of the cube 
and drag it to the right of "Expense" - you now have expenses by department. Left 
click on "Department" again and drop on the left of "Expense" [near the margin] - you 
now have a departmental expense analysis, and not a "query" in sight. It is this 
"interactive" nature of a "cube" that adds value to the equation)

Ross Ferris
Stamina Software
Visage - an Evolution in Software Development

>-----Original Message-----
>Sent: Monday, 19 April 2004 5:20 AM
>To: U2 Users Discussion List
>Subject: Re: GUI from Mv code Re: Crystal Reports
>In a message dated 4/18/2004 10:18:11 AM Eastern Daylight Time,
>> For example, aligning this back to the original post, rather than
>attempting to use CR for reporting, I'd simply create a Viságe.BIT cube to
>give the users free-form enquiry and data exploration facilities into their
>UV database. In our case we have replaced >300 sales analysis reports
>currently provided in our R5 system with a single Sales Cube -   and this
>is one of the facilities that makes Viságe "better" than
>> AccuTerm !
>Warning! Salesman quote!
>C'mon Ross :) A dataset that includes 50 fields and I only want to see 6 on
>my report.  So you replace that report with a cube where I (the user) have
>to figure out exactly what I want to see, build the proper query statement,
>format statement, display statement etc and then figure out how to tell the
>system to remember my statement so next time I don't have to THAT all
>You replaced the 300 reports, with one huge cube where you STILL have users
>recreating (or trying to) their original 300 reports...
>   Users don't want to see 50 fields, they want to see the 6 fields they've
>been analyzing for the past 3 years ...
>u2-users mailing list
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (
>Version: 6.0.659 / Virus Database: 423 - Release Date: 15/04/2004

Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
Version: 6.0.659 / Virus Database: 423 - Release Date: 15/04/2004
u2-users mailing list

Reply via email to