Spooled file size
Greetings to everyone in this group.
I still have a question: why is RB spool size so big?
I have noticed that it is almost always double as (for example) size of the
graphics being printed.
If a bitmap is 64K, and printed alone on the report page, spooled report
file will be at least 150K, sometimes it goes over 200K.
What is the trick? Can we manually lower print resolution, if it is a reason
to generate so big spool size?
More examples:
image (8MB bitmap in memory) : spool size: 25M
image (2MB bitmap in memory) : spool size: 8M
What the hell makes spool file 4x bigger than the image printed?
I suppose that maybe printing routine enlarges print size depending on a
resolution of the printer. Can we fix printing resolution manually to, for
example, 100dpi without changing printer settings?
TIA,
Davor
I still have a question: why is RB spool size so big?
I have noticed that it is almost always double as (for example) size of the
graphics being printed.
If a bitmap is 64K, and printed alone on the report page, spooled report
file will be at least 150K, sometimes it goes over 200K.
What is the trick? Can we manually lower print resolution, if it is a reason
to generate so big spool size?
More examples:
image (8MB bitmap in memory) : spool size: 25M
image (2MB bitmap in memory) : spool size: 8M
What the hell makes spool file 4x bigger than the image printed?
I suppose that maybe printing routine enlarges print size depending on a
resolution of the printer. Can we fix printing resolution manually to, for
example, 100dpi without changing printer settings?
TIA,
Davor
This discussion has been closed.