By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,311 Members | 1,839 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,311 IT Pros & Developers. It's quick & easy.

Memory usage for reports

P: n/a
I have an Access 2002 database. BE is only about 25MB located on a NT4
server. The front end is an MDE file located on the local workstations
(XP, 512 RAM, 40Gig HD) running Access Runtime (scripts built by
SageKey). I have a report based on a query (pulls about 10K records
w/o the where clause that is used prior to printing). In order to get
the printer to see all 4 copies as one job and staple it I have a
report shell with 4 subreports (all identical) which creates 4 copies
of the ticket. The ticket does have a logo and a lot of lines (like
filling in a form). It works fine but runs slow. The printer
(Gestetner DSm627 RPCS) is setup with it's own IP address on the
server.

After hitting the print button it is now taking almost 60 seconds to
start printing. Opening the print que window shows it spooling for
most of the time and then it counts off the pages 1/4 etc. It use to
be faster but seems to keep slowing down. All my other basic reports
(even a 86 page customer list) starts printing right away.

My question is what type of memory/temp files (an where - server vs
client) does Access use to process/spool and print reports? Just RAM /
Virtural Memory / temporary spool folders / ??

Any help would be greatly appreciated.

Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On 3 Feb 2005 16:41:04 -0800, sr*****@tcrsoftware.com wrote:

All processing is taking client-side. Access is not a client/server
app.
How long does it take to run the report's underlying queries? Perhaps
something can be optimized there (indexes).
If you can avoid it, don't use "page N of M", because that requires
all formatting to be completed before the first page can be output.
Try modifying the report and take out all lines. If that prints A LOT
faster, you know what your trade-off is.

-Tom.
I have an Access 2002 database. BE is only about 25MB located on a NT4
server. The front end is an MDE file located on the local workstations
(XP, 512 RAM, 40Gig HD) running Access Runtime (scripts built by
SageKey). I have a report based on a query (pulls about 10K records
w/o the where clause that is used prior to printing). In order to get
the printer to see all 4 copies as one job and staple it I have a
report shell with 4 subreports (all identical) which creates 4 copies
of the ticket. The ticket does have a logo and a lot of lines (like
filling in a form). It works fine but runs slow. The printer
(Gestetner DSm627 RPCS) is setup with it's own IP address on the
server.

After hitting the print button it is now taking almost 60 seconds to
start printing. Opening the print que window shows it spooling for
most of the time and then it counts off the pages 1/4 etc. It use to
be faster but seems to keep slowing down. All my other basic reports
(even a 86 page customer list) starts printing right away.

My question is what type of memory/temp files (an where - server vs
client) does Access use to process/spool and print reports? Just RAM /
Virtural Memory / temporary spool folders / ??

Any help would be greatly appreciated.


Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.