Ok, well thats a good bit of feedback :-)<br>I seemed to remember that it output to PDF, but does it also export to Excel too?<br><br>Most of our data is pretty basic. the most complex it gets is that it requires grouping. <br>
I guess I need to workout our most complex report, and see how I go reproducing that.<br><br>Thanks, Jeremy<br><br><br><div class="gmail_quote">On Mon, Dec 1, 2008 at 9:24 AM, Max Nilson <span dir="ltr"><<a href="mailto:max@accredo.co.nz">max@accredo.co.nz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Jeremy Coulter asked:<br>
<div class="Ih2E3d"><br>
> Does anyone use Rave Reports in their apps. ?<br>
</div>> What have been your experiences. From memory you have to supply a DLL<br>
<div class="Ih2E3d">> or maybe 2 with your app. install?<br>
<br>
</div>Yes, we use RAVE, or more correctly RPPro in the Accredo Business<br>
Software suite (nee Profax Accounting), and we have done so for about 10<br>
years.<br>
<br>
As shipped it's a totally Delphi sourced based distribution and has<br>
various layers that you can work at for generating reports. Originally<br>
it was a very good code based reporting engine called RPPro, and that is<br>
the level at which we still use it. This provides us with a fairly good<br>
insulation from the actual Windows printing device model and allows for<br>
various outputs to be generated from it. The mains ones that we use are<br>
the printer output, and the PDF output engines.<br>
<br>
Over the years Nevrona decided to add a full user report design surface<br>
and renamed the package RAVE, but after looking at RAVE we decided that<br>
we were better off writing our own domain specific report designers and<br>
totally ignoring the RAVE designer. Other may feel differently but it<br>
really depends on the data you are reporting from and the level of user<br>
skill that your product has.<br>
<br>
There are one or two remaining gremlins in the RPPro reporting engine<br>
that I have hacked around over the years, the two most annoying were<br>
handling the printer naming mess that occurs in Terminal Server<br>
situations, and the lack of elegant font embedding technology in the PDF<br>
output engine.<br>
<br>
Happily there are various third (or is that forth?) party solutions to<br>
the PDF output from RPPRo side of things and you can buy some very<br>
advanced PDF output stuff that will to all the PDF magic you may ever<br>
need.<br>
<br>
Overall I recommend RAVE/RPPro as a package, but be warned that Nevrona<br>
have focused heavily on the RAVE side of things over the last 5 years<br>
and have been ignoring any improvements to the RPPro code based layer,<br>
and have made minimal patches to issues in it over the last 4 or 5<br>
releases. Now that they concentrate on RAVE they are letting RPPro<br>
slowly stagnate so long as its supports RAVE that's all they care about,<br>
as its their primary market.<br>
<br>
Cheers, Max.<br>
<div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
NZ Borland Developers Group - Delphi mailing list<br>
Post: <a href="mailto:delphi@delphi.org.nz">delphi@delphi.org.nz</a><br>
Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
Unsubscribe: send an email to <a href="mailto:delphi-request@delphi.org.nz">delphi-request@delphi.org.nz</a> with Subject: unsubscribe<br>
</div></div></blockquote></div><br>