Memory for rendering a report page

[anthony]

Does Access limit the amount of memory needed to render a report page?
If so, is it possible to increase the default?

 

[Adnan]

Type a question (i.e., Access specifications) on help filed of access window.

--
HTP
Adnan

If I have helped and/or answered your question, please let me know by
replying or clicking question answered (below positioned ‘Yes’ button).

 

[Marshall Barton]

Does Access limit the amount of memory needed to render a report page?
If so, is it possible to increase the default?

Access dynamically allocates the memory it needs.

Why don't you describe the problem you are having? Maybe
someone will have a more useful diagnosis.

 

[Stephen Lebans]

To reduce your memory foot print per page you must:

1) Use the Print event, NOT the Format event, to load your images into the
Image control.

2) Turn off the Loading Image dialog via the Registry.

This is an old Bug caused by the "Loading Image" dialog. Here is a previous
post of mine on this issue.

If you do not stop the "Loading Image" Dialog via the Registry modification
you will run into two issues:


1) Access can crash if you scroll through the records too fast.


2) When printing a Report, Access may run out of resources and be
unable to complete printing the report.


Additionally, two issues in regards to the Registry modification
pointed to
here http://www.mvps.org/access/api/api0038.htm


1) The Registry key MUST be "No" NOT "no" or "NO"


2) On systems with XP or on systems with more than one user account,
you must add/modify the key in both HKEY_CURRENT_USER and
HKEY_LOCAL_MACHINE.


------------------------------------------------------------------------


If after modifying your MDB for #1 and #2 above still leaves you with a lack
of resources to complete the print job then you can try:

3) Use the fLoadPicture function on my site to load your large images into
the Image control.
http://www.lebans.com/loadjpeggif.htm


Finally, if implementing all of the above does not resolve your issue then
you will have to programmatically print out a few pages of your report at a
time.

--

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

 

[anthony]

Access can crash if you scroll through the records too fast

Ah, so that why it happens!

That's it - actually, it seems to run out of resources on the page and
fail to print some of the photos unless I reduce their sizes first

ACCDB in this particular case

I'll follow your advice, for which many thanks, as usual

Anthony

 

[anthony]

Why don't you describe the problem you are having?

Simply, that Access is failing to print six images per A4 page when
the images are left at their original size (between 1.3MB and 1.8MB).
If I reduce the size, everything is OK. Stephen has given me several
things to try which I will do now

 

[Marshall Barton]

Simply, that Access is failing to print six images per A4 page when
the images are left at their original size (between 1.3MB and 1.8MB).
If I reduce the size, everything is OK. Stephen has given me several
things to try which I will do now

Ahhh, images. Images can be a problem. Stephen is the
expert on this issue.