Report, w/ graphics, getting clobbered on way to the printer...

[Guest]

I have a report that includes linked .bmp's. When the report has many images
to print, and the memory used by access gets somewhere over 1gb, than I end
up getting many blank pages. The page that the blanks start on is different
depending on which printer is selected. Also, these long reports are unable
to be turned into .mdi or .pdf files.

Is there an intrinsic limit in access that I am exceeding? Any idea how to
resolve this? Will future versions of access address this issue? Is this
NOT an access issue at all but a OS issue? Would some other report writer
(crystal) be a better solution?

Can't wait to hear from you guys!

-Mike

 

[bob]

It sounds like you are simply running out of Virtual Memory. Access generates the complete report in VM
before spooling it to the printer. In reports with images this can use a lot of VM.

If you configure sufficient VM you should find that your reports run fine. On Win 9x series platforms
defragging is often enough to make sufficient VM available.

Reducing the resolution of your images would reduce the VM required, but may reduce the quality of your
output too.

 

[Stephen Lebans]

Do you have the "Loading Image" dialog turned off via the Registry?

How many pages is your report?

Are you loading your graphics/Images into the standard Image control, via
its Picture property, or are you using an OLE Frame control instead?

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.

 

[Guest]

I have not turned off the registry value for loading images, because I am
using .bmp files which do not require any translation and, so, no dialogue
appears. Would tweaking those registry values help anyway? The images are
loaded into the standard image control, which is being controlled by a field
that holds the path and file name.

Reports vary in length from 18-200 pages. The length of the report does not
matter, just the amount of RAM being used which is directly related to the
number of images (which is a variable amount for each page... Depends on the
result set being printed).

It seems that Access is just not recovering well from whatever the major
memory problem is. One thing I am theorizing is that I am bumping into the
internal 4gb ram limit (2gb + 2gb) and am wondering if setting the secret
switch to reconfigure from 2gb+2gb to 3gb+1gb would work.

-Mike

 

[Stephen Lebans]

What version of Access and Windows are you using?

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.

 

[Guest]

Hi Stephen!

I have Access 2003 running on Windows XP (I am assuming it is XP PRO because
it is on a corporate network at work).

-Mike

 

[bob]

Have you verified that you are not exceeding available virtual memory by monitoring PF usage (in Task Manager)
while the report runs ? It sounds like you have already discounted this possiblity, but just in case,
the following may be useful:

How to overcome 4,095-MB paging file size limit in Windows
http://support.microsoft.com/kb/237740/en-us

 

[Guest]

Stephen,

Is it possible that my reports are being blasted away due to the the way
Access processes a report? Would a different report writer be a worthy
investment? Or, should I explore some other way of sidestepping the issue
inside of Access, or wait for the upgrade and hope for the best (not a great
option)?

Thanks for your thoughts...

-Mike