BUGS in Report Preview????

  • Thread starter Thread starter Bill Stanton
  • Start date Start date
B

Bill Stanton

Running W98SE, Office 2000 SP3 with 512MB
Ram, I've been developing a report that contains
12 jpg images plus a multi-line text-box per page
and with 12 to 13 pages with the current Record-
Source.

As debug and adjustments proceed, with extensive
use of "Preview", I get a message indicating that
there is not enough memory to continue at a point
where I want to advance to the next page using
the navigation button, say from page 8 to page 9.
Aside from my primary question forthcoming, why
doesn't VM handle such an overflow?

The real problem:
After shutting down Access and wanting to proceed
to another task, nothing will start for lack of memory.
At that time, I have no windows open and the only
thing running in the background are core-group tasks
like Norton NIS/AV, ICSmgr, etc. I have to re-boot
to clear up the memory issue.

It appears that A2K report preview allocates storage
but does not free it upon completion. I would have
expected that AT LEAST Windows would have
freed any storage allocated on behalf of Access when
the task ended. With the exception of the foreign
language patches, I've installed all the latest updates
to Win98SE and I have no memory failing symptoms
outside the use of Access.

Are there any known bugs in A2K with regard to
memory allocations? If not, does anyone have
thoughts about this problem?

Thanks,
Bill
 
Larry,
I read a couple of articles at Lebans' website dealing with
images. It's not at all clear to me that what problems are
described there apply to my situation, unless the rendering
code that displays the jpeg images at load/run time are
misbehaving with regard to storage allocation/freeing.

My super imposed unbound OLE and image controls link
dynamically to the desired images stored in an image folder,
which avoids the "OLE bloat" problems described in one of
the articles. The images preview and print perfectly, so I don't
have any complaints there. But, at seems clear that whatever
storage was allocated during the process is not freed either
by A2K or Win98SE.

Did you see R. Adams' post "Memory error"?

Bill
 
Bill,

I have several reports that use images. My experiences
suggest that using bitmaps is preferable to any other
format, I don't have a good reason for this ... it just
is. When printing large reports I eventually get some
errors writing to the printer object. This occurs 10,000
pages into a report using bitmaps and about 2,500 pages in
using other formats. Memory usage goes up and up and up. I
use win2k as an operating system and this does return the
memory after Access has done it's thing (the NT kernel may
be better at this). No experience using with win98.

Generally I use an image control with the picture property
pointing at the file in the file system. Set this in the
section's on format event if using variable images.

Not much in the way of fixes I'm afraid.

HTH,

Terry
 
Back
Top