[DUG] QuickReports 4.05 issues

[Hayward, Phillip]

Using QuickReports 4.05 I have developed a report that is actually two
reports in one, eventually to be three. To tie them together I have used
a TQRCompositeReport component and run the reports like such...

QRCompositeReport1.Preview;

And use the onAddReports event to call....

procedure TForm1.QRCompositeReport1AddReports(Sender: TObject);
begin
  QRCompositeReport1.Reports.Add(fDeliveryItemRpt.QuickRep1);
  QRCompositeReport1.Reports.Add(fDeliveryItemRpt2.QuickRep1)
end;

The report runs without issue but when the application is closed I get
an 'Exception EAccess Violation in module....' error and at times the
desktop practically locks up requiring a reboot.

I believe it is tied to the TQRCompositeReport because if I don't use
the component and run the reports individually ...

fDeliveryItems.fDeliveryItemRpt.QuickRep1.Preview;
fDeliveryItems2.fDeliveryItemRpt2.QuickRep1.Preview;

there is no issue.

Last year we applied a patch to version 4.05 to fix memory leaks. This
was just a matter of applying 

if QRPrinter <> nil then QRPrinter.free; 
to 
Destructor TCustomQuickRep.Destroy;
in quickrpt.pas and recompiling .

Now, why I mention this is during debugging it seems to be here that the
error is caused when exiting the program.

We considered upgrading to version 4.06 in the hope that all these
issues would have been resolved but then found we couldn't compile any
of the previous applications developed with version 4.05

Has anyone else experienced like such issues with QuickReports and more
importantly the TQRCompositeReport component?

Should we perhaps be looking at another report engine moving forward?


Regards 
Phil Hayward

System Analyst 
Pinepanels Rangiora
ph  (64) 3 313-2764
fax (64) 3 313-2739
Ext 38824
Phillip.Hayward at chh.co.nz


DISCLAIMER: This electronic message together with any attachments is 
confidential. If you are not the intended recipient, do not copy, disclose or 
use the contents in any way. Please also advise us by return e-mail that you 
have received the message and then please destroy. Carter Holt Harvey is not 
responsible for any changes made to this message and / or any attachments after 
sending by Carter Holt Harvey. We use virus scanning software but exclude all 
liability for viruses or anything similar in this email or any attachment.