cancel of printjob -> error
Hello,
when I cancel a printjob useing the cancelbutton of the canceldialog,
and I click on the cancelbutton many times, because it doesn't cancel
imediatly, I get an error: "index out of range"
It comes of any kind of a tlist object.
I could not find out, why the problem occures, but I could do a
workaround by inserting
btncancel.enabled := false
into the onclickevent of the btncancel in the unit ppCDlg.
So the btncancel is disabled after the first click and the error could
not occure.
Now it works for me, but I if I upgrade to the next version of
Reportbuilder, the problem will be there again, if I forget to change
it again.
Do you see any possibility to solve this problem in the next release?
cu
Helmut
when I cancel a printjob useing the cancelbutton of the canceldialog,
and I click on the cancelbutton many times, because it doesn't cancel
imediatly, I get an error: "index out of range"
It comes of any kind of a tlist object.
I could not find out, why the problem occures, but I could do a
workaround by inserting
btncancel.enabled := false
into the onclickevent of the btncancel in the unit ppCDlg.
So the btncancel is disabled after the first click and the error could
not occure.
Now it works for me, but I if I upgrade to the next version of
Reportbuilder, the problem will be there again, if I forget to change
it again.
Do you see any possibility to solve this problem in the next release?
cu
Helmut
This discussion has been closed.
Comments
When the cancel button is pressed, ReportBuilder will not cancel the report
until the current page has been printed. Which version of ReportBuilder are
you using. Have you tested this with a trial version of RB 7.03? In my
testing, I was unable to recreate the error by pressing the cancel button
more than once.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
I use Reportbuilder 7.03 Enterprise. Not the trial version.
I think you have to print a report, where the printing of one page
lasts a few seconds (a slow query or soemthing else), so that you have
the time to press cancel a few times.
I can reproduce the error, but it doesn't occure everytime. I think it
is a timecritical problem.
cu
Helmut
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com