Since the customer want to see sections of it.. you can speed it up by going to the first record that they wanna see.. You can use Locate etc ...
OnNeedData is called everytime QR need data (obviously)..
So when you issue QR1.Print or QR1.Preview, QR will call
the OnNeedData.
Here you must...
1.9 million record will take forever to print, even on the fastest printer.
Why don't you break the data up, say into 19 reports, so around 100K records/report. Or 190 reports for 10K records/report.
Bottom line is, break the data into small chunks. It'll be easier to deal with.
You can...
Umm.. do you still need answer to the 'Does anyone know why?' on your 1st post? :D
Cause you solved it already. :) I think I only wanna add some comments, and try to answer your Q: why the AV exceptions.
EAccessViolation (AV) are exceptions raised when you try to access invalid part of memory...
Steven, you can use an explicit TDatabase and point all your dataset Database property to there. Once you turn the TDatabase.Active to False in the Object Inspector and build your proj, you can be absolutely sure that no data access in yhour OnCreate event.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.