RE: McKoi and Inetsoft Style Reports Problem

Have you considered SCRIBE? It works with McKoi, among other RDBMS, and
from what I see on the InetSoft's website, provides more functionality
(e.g. I do not see drill-down on cascading reports there). The Personal
edition is free, and the Enterprise edition is priced at about 1/10 of
Style Report.

A writeup on SCRIBE came out on Jan 18 in the Java Developers Journal
(http://www.sys-con.com/story/?storyid=47744&rss=1)

If you are interested, visit www.reportgenerator.org.

Regards,

Alex Molochnikov
Gestalt Corporation



-----Original Message-----
From: Rich Davis [mailto:[email protected]] 
Sent: Tuesday, March 08, 2005 6:33 PM
To: [email protected]
Subject: McKoi and Inetsoft Style Reports Problem


Hello,

I have been trialing a product by inetsoft called Style Reports. (  
http://www.inetsoft.com/inetsoft/products/prodoverview.html  )

I have run into a problem when trying to use this product with McKoi.

Basically, they have an SQL wizard / builder but it cannot cannot 
retrieve the DB fields from McKoi.  For example, in the screen shot 
below you will notice that the "msg" table does not show the fields of 
the table and the subsequent build functions are blank (Fields, 
conditions, sort grouping)

<I couldn't send the screen shot; too big>

A different feature of the builder (the "physical model"  view) the 
product can show the fields.  When I opened a case with their support 
they pointed me to this issue on the McKoi list:

http://mckoi.com/database/mail/subject.jsp?id=5898&highlight=column+null
+type+#MSG_5898

And here was his explaination when I explained that McKoi works in one 
portion of their product wizard and not in another:

It is hard for me to speculate the exact reason for this, as I have to
factor in the database driver too. The reason I think this happens is
because for physical models we do not consider column types, whereas
while building queries we do, and since the database driver is known to
return null for column types this is a probable cause. Please refer to
the link for more information.


Do you think their explaination makes sense?  Do you think McKoi is the 
cause and if so do you think it is fixable?  The existing list document 
indicates that McKoi works to the specification but that does seem to be

problematic in this case if it is the cause.  Any help would be greatly 
appreciated. 

Thanks,

Rich Davis




---------------------------------------------------------------
Mckoi SQL Database mailing list  http://www.mckoi.com/database/ To
unsubscribe, send a message to [email protected]



---------------------------------------------------------------
Mckoi SQL Database mailing list  http://www.mckoi.com/database/
To unsubscribe, send a message to [email protected]