From: Doug Phelps
> Eddy Jacobs wrote:
>
> "Rune Randøy" wrote:
>
> >Anyone out there using Crystal Report on Ingres databases ?
>
> >We are running Ingres 6.4/04 on various unix platforms, with reports written
> >in ReportWriter. The "online" part of our application has now been ported
> >to OpenROAD (we used A2W), and we are now looking at what our options for
> >the reports are.
>
> >I guess we need ODBC to get from Crystal Reports to Ingres. Most of our
> >reports contains SQL-statements in .SETUP. Is there any way to do this
> >with Crystal ?
>
> >Crystal Reports also has a "Report Server", which we do not know too much
> >about. Does it run on Windows only? NT? Unix?
>
> >If anyone has used these products with Ingres I would be most grateful to
> >hear your opinion. If you looked into it and decided not to do it, it would
> >be interesting to know why.
>
> Hello,
>
> For the last 2 months we have been trying out several Report Writers
> to use with Ingres (on Windows 3.11 and Windows 95 clients).
>
> We evaluated the products based on:
> 1) the possibilities to create every report no matter its complexity.
>
> 2) the way of 'communicating' with the Ingres Server (ODBC or native
> Ingres-net). It is clear that it all depends on the ODBC driver you
> choose (there are a lot of discussions going on in this group about
> ODBC). Personally I prefer 'native Ingres-net'-communication.
>
> 3) the way of 'communicating' with the OpenRoad client (DDE or
> script-files). We had some bad experience in the past with
> DDE-communication, so we are very sceptical about it. We prefer the
> possibility to boot the reportwriter from within OpenRoad and pass
> parameters to the report-writer by means of command-line options or a
> parameter-text-file which can be read by the report. The advantage of
> DDE however is that one does not have to load the reportwriter every
> time a report has to be executed.
>
> Here are the test-results:
> 1) Visual Express : report-possibilities : not bad.
> Server-communication : ODBC
> Client-communication : DDE. terrible, very unstable.
>
> Another major drawback : if we had an existing report and we wanted to
> change the table structure (add a field) we had to recreate the whole
> report. This was really unacceptable.
>
> 2) IQ-objects : report-possibilities : to limited.
> Server-communication : ODBC from Intersolv (via Ingres Net)
> Client-communication : command line parameters (very good)
>
> The only way to create user-defined function is by creating his own
> DLL's and link them into IQ-objects. Due to its lack of having a
> macro-language, we quickly ran into the limits of the product. It's a
> pitty because it has a really nice way of doing things.
> Like I already said the fact of working with command line parameters,
> meens that you have to reload IQ-objects every time you execute a
> report.
>
> 3) Crystal Writer report-possibilities : good (own macro
> language)
> Server-communication : ODBC
> Client-communication : DDE (not our first choice)
>
> We did not really got into Crystal Writer because we don't like DDE as
> the only way of passing parameters to a reportwriter.
>
> 4) ReportSmith 2.5 for SQL-databases from Borland.
> report-possibilities : nearly unlimited because of its very
> powerful macro language (ReportBasic).
> Server-communication : native Ingres Net or ODBC
> Client-communication : DDE or by means of a
> text-parameter-file
> which is read by the report.
>
> We have been testing this reportwriter for 4 days now, and until now
> we are very enthusiast (but so were we in the beginning with Visual
We are evaluating Compuware's Ecotools product and one of the databases
that we have and not supported by Ecotools is Ingres.
Is there anybody that has written their own agents to monitor ingres from
within Ecotools?
You can e-mail me with any responses at
Doug.Phelps@corp.honeywell.com
TIA
-
Ingres Q & A
-
To William's Home Page
© William Yuan 2000
Email William