Blank result generate unendless pages and other problem
I don't know if this is the correct newsgroup to post...
I use End user report manager, (but the proble still alive in any report
project) I set in the report some search criteria: when searching wrong
parameters I've no result, the report is blank but have unendless pages.
If I print the report it continue printing...
When I show preview report, the hourglass and "reading data" state, still
remain on screen.
Have oyu some suggestion?
thanks
I use End user report manager, (but the proble still alive in any report
project) I set in the report some search criteria: when searching wrong
parameters I've no result, the report is blank but have unendless pages.
If I print the report it continue printing...
When I show preview report, the hourglass and "reading data" state, still
remain on screen.
Have oyu some suggestion?
thanks
This discussion has been closed.
Comments
Have not heard of this before. What version of ReportBuilder are you using?
(Check the Help | About box of the Report Desigenr).
Can you recreate this error using the RBuilder\Demos\EndUser\Report Explorer
example app? Please specify exact steps to reproduce this issue.
--
Nard Moseley
Digital Metaphors
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
I think that I don't be able to reproduce this because i0ve reimplemented
connection (I'm using a tecnology similar to ASTA)
now I will try and after I post this here
the problem is mine, i've tried your suggestion:
i place a label into header of a report; in enduser project no problem, in
myproject the result it's like a unendless report..
now i must find the problem, but i've no idea
I think it's something that call a pagecalculation... but I can't find it...
"Tefnut" ha scritto nel messaggio
Try setting the Band.PrintHeight properties to phDynamic. If Band
PrintHeight is set to phStatic and the sum of the margins plus band heights
exceed the physical page height then you can get infinite pages.
Try commenting out all event-handler code associated with the report. Make
sure that you do not have any code that manipulates the dataset while the
report is excuting. This can cause the report engine to get lost.
Debugging the report engine is very very difficult. There are many complex
steps. Try reconfiguring the report to get it to work correctly. If you want
to create an example using RB and DBDemos you can e-mail to
support@digital-metaphors.com and we can check it out here.
--
Nard Moseley
Digital Metaphors
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com