Well, we can certainly help you on the latter front (OLAP/BI software
that works well with D3) with our Visage.BIT product. You can play with
a cube yourself, and also download a white paper from here
http://www.stamina.com.au/Products/V...Visage_BIT.htm
You don't have to worry about "joins" (inner, outer or left-behind)
because Visage.BIT understands mv data structures (we don't care HOW
deep), translates etc, and there is also a powerful API that allows you
do do some really "interesting" things, like producing cubes on
information that ISN'T present in the database (watch for an upcoming
article).
As Visage.BIT uses MOLAP technology, you can also have H U G E cubes
- we have clients with cubes that have over 30 dimensions from
millions of source records, and you can have ANY combination of
dimensions (not limited by preset views required for ROLAP optimation)
allowing you do undertake data discovery in a free-form "explorer"
style,
Like all of the Visage range, BIT can be installed as a "stand
alone" product, or be deployed as an integral component of the total
Visage application development suite.
Custom views can be saved for later recall, and shared for standard
reporting, and a current "view" can be exported to Excel with a
single button click
Ross Ferris
Stamina Software
Visage > Better by Design!
On Oct 12, 3:41 am, "skypirate" <sing... (AT) singdad (DOT) no-ip.com> wrote:
Quote:
Hi,
Have already confirmed by RD, their ODBC driver will not support 'Inner
Join' , 'Outer Join' syntax and they are not going to enhance it as
well. As most of the OLAP reporting software or BI reporting software
are using such statement to join the tables.
Any idea how can I archieve such kind of table linking in D3?? or any
3rd Party ODBC driver is available in the Market? or any Window based
OLAP/BI software works well with D3?
Rgds, |