Anonymous Logon & BIG BIG BIG reports
Okay here are my problems (2)
Problem 1 :
Sometimes, just sometimes I get problems with printing. The documents owner
is 'ANONYMOUS LOGON'
the whole spooler hangs and you can't delete the job by hand.
You don't get a warning whatsoever if the problem occured only that there
isn't coming anything out of the printer
Problem 2 :
When printing something, which are most of the times are only 1 page
sometimes 2, it occasionally produces an enourmous amount of paper >1000 is
no exception. What is causing this problem ?
Any got a clue ?
Yours truly,
Paul
Problem 1 :
Sometimes, just sometimes I get problems with printing. The documents owner
is 'ANONYMOUS LOGON'
the whole spooler hangs and you can't delete the job by hand.
You don't get a warning whatsoever if the problem occured only that there
isn't coming anything out of the printer
Problem 2 :
When printing something, which are most of the times are only 1 page
sometimes 2, it occasionally produces an enourmous amount of paper >1000 is
no exception. What is causing this problem ?
Any got a clue ?
Yours truly,
Paul
This discussion has been closed.
Comments
board.
2. Please follow the guidelines below to help you resolve this issue.
--
Cheers,
Alexander Kramnik
Digital Metaphors
Article: TroubleShooting: Report Prints Endless Pages
------------------------------------------------------
Occasionally, we have customers state that their reports are in some
infinite state where page after empty page prints forever.
There are a few items to check when this occurs.
The TppReport.AutoStop property is the first thing to check. If this is
false when the DataPipeline property is unassigned, the endless report will
be the result. AutoStop is automatically set to True when DataPipeline is
set to nil, but it is possible to set it back to False. Check for instances
in your code where you might have created this condition.
Another thing to check is that all subreports in your report have their
DataPipeline set. When a subreport does not have its pipeline set, you will
sometimes see a condition where the first detail record prints and then you
get blank pages.
Another, non-data related cause can sometimes be your margin settings. If
you have stretching bands that need to overflow to the next page, if your
margins are too tight, sometimes the report engine will endlessly overflow
to the next page trying to fit the overflow material. As a test, try setting
DetailBand.PrintHeight to phDynamic. A dynamic height band can overflow to
additional pages as needed.
Still another cause might be having a statically positioned control, set to
ReprintOnOverFlow, in the same band with a stretching control. For instance,
if you have a memo set to stretch and in that same band, a label control set
to ReprintOnOverFlow, then on every page after the first, the memo will
begin to print after the label control. If the label is placed low enough
that the memo has no room to print, the report will forever be trying to
print the overflowing memo on the next page.
http://www.digital-metaphors.com
info@digital-metaphors.com
2. Thank you, wil look in to it.
Yours truly,
Paul Menheere
"Alexander Kramnik (Digital Metaphors)" wrote
security settings on the machine? Do some of them perhaps not have proper
permission to print?
--
Cheers,
Alexander Kramnik
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com