Microsoft Graph Too Slow

[Guest]

I am currently using Microsoft Graph in a dynamic report that enables users
to select and compare (overlay) up to 8 series. Each series plot has about
10-13 data points.

The report has 30 graphs total (2 per page), and about 40% of the graphs
utilize derivative data that is calculated as the report is printing.

The problem is this: each page in the report takes about 15-20 seconds to
finish printing. The end-users of my distributed application would, of
course, prefer this to speed up a bit.

I have attempted to streamline and optimize the underlying code to make it
as efficient as possible, but this had no appreciable effect.

Is this slowness just an inherent limitation of MS Graph, or is there
something I can do to speed things up significantly? And if it is a weakness
of MS Graph, are there any viable alternatives that I can use in the MS
Access report objects?

Any advice would be greatly appreciated.

 

[Larry Linson]

I am currently using Microsoft Graph in
a dynamic report that enables users
to select and compare (overlay) up to 8
series. Each series plot has about
10-13 data points.

The report has 30 graphs total (2 per page),
and about 40% of the graphs utilize deriva-
tive data that is calculated as the report
is printing.

The problem is this: each page in the report
takes about 15-20 seconds to finish printing.
The end-users of my distributed application
would, of course, prefer this to speed up a bit.

I have attempted to streamline and optimize
the underlying code to make it as efficient
as possible, but this had no appreciable effect.

Is this slowness just an inherent limitation of MS
Graph, or is there something I can do to speed
things up significantly? And if it is a weakness
of MS Graph, are there any viable alternatives
that I can use in the MS Access report objects?

There are certainly third-party controls for presentation of data, including
many kinds of graph. I am not personally acquainted with anyone using these
with Microsoft Access, though I know some who've used various ones in
classic VB applicatiions. There are a multitude of third-party controls, but
relatively few designed to be compatible with Access.

You didn't say what your execution environment is: single-user standalone,
multiuser Access - Jet, or Access client to server database. That could make
a difference, and even low level code used in calculating the derivative
data could slow you down.

If it is multiuser, in addition to standard speed-up techniques, such as
making sure that each table has a primary key, and using indexed fields in
any Joins and WHERE clauses in the Queries, etc., MVP Tony Toews' site has
the best information and links on multiuser performance that I have found at
http://www.granite.ab.ca/accsmstr.htm.

Larry Linson
Microsoft Access MVP