Error when printing report

  • Thread starter Thread starter Rob Parker
  • Start date Start date
R

Rob Parker

I have a report, containing three subreports, two of which contain chart
objects. This report opens fine (although rather slowly - the underlying
queries are quite complex) in preview mode, but when I try to print it I get
an error message "Cannot open any more databases"; when I click OK to
dismiss this message, I immediately get another error message "An error
occurred while sending data to the OLE server (the application used to
create the object)." The report then prints, but is missing the chart on
the second subreport (and an additional blank page appears after that
subreport). The chart on the third subreport prints OK.

If I open the offending subreport directly I am able to print it with no
errors occurring.

The second error message has several suggestions, as follows:
* You may have tried to send too much data. If you're creating a chart and
the chart is based on a query, modify the query so that it selects less
data. If the chart is based on a table, consider basing it on a query
instead so that you can limit the data.
* You may be using an OLE server that doesn't accept the clipboard format.
* You may not be able to start the OLE server because it's not properly
registered. reinstall it to register it.
* Your computer may be low on memory. Close other application windows to
free up memory.

None of these seems applicable. The chart on the second subreport is less
complicated than the chart on the third subreport (4 data series each with
12 points plotted against one y-axis, compared to 6 data series each with 12
points plotted against two y-axes). The OLE server certainly works, since
the subreport prints with its chart when printed alone, and the chart on the
third subreport prints OK. The error occurs on two systems, both of which
are running Windows XP Pro (fully up-to-date with service packs), and which
have 2GB RAM. Closing all other applications does not affect the problem.
Both systems are running Access 2003, fully patched with all service packs
and hotfixes.

Any suggestions on why this is occurring and how to fix it will be
gratefully received.

TIA,

Rob
 
Rob Parker said:
I have a report, containing three subreports, two of which contain chart
objects. This report opens fine (although rather slowly - the underlying
queries are quite complex) in preview mode, but when I try to print it I
get
an error message "Cannot open any more databases"; when I click OK to
dismiss this message, I immediately get another error message "An error
occurred while sending data to the OLE server (the application used to
create the object)." The report then prints, but is missing the chart on
the second subreport (and an additional blank page appears after that
subreport). The chart on the third subreport prints OK.

If I open the offending subreport directly I am able to print it with no
errors occurring.

The second error message has several suggestions, as follows:
* You may have tried to send too much data. If you're creating a chart and
the chart is based on a query, modify the query so that it selects less
data. If the chart is based on a table, consider basing it on a query
instead so that you can limit the data.
* You may be using an OLE server that doesn't accept the clipboard format.
* You may not be able to start the OLE server because it's not properly
registered. reinstall it to register it.
* Your computer may be low on memory. Close other application windows to
free up memory.

None of these seems applicable. The chart on the second subreport is less
complicated than the chart on the third subreport (4 data series each with
12 points plotted against one y-axis, compared to 6 data series each with
12
points plotted against two y-axes). The OLE server certainly works, since
the subreport prints with its chart when printed alone, and the chart on
the
third subreport prints OK. The error occurs on two systems, both of which
are running Windows XP Pro (fully up-to-date with service packs), and
which
have 2GB RAM. Closing all other applications does not affect the problem.
Both systems are running Access 2003, fully patched with all service packs
and hotfixes.

Any suggestions on why this is occurring and how to fix it will be
gratefully received.

TIA,

Rob
Click to expand...
 
If your record sources and row sources are too complex, then you need to
simplify them. It's difficult to suggest any changes to your SQL statements
without seeing them.

At times you my just create temporary tables prior to opening the report.
This removes most of the complexity and your reports will render much more
quickly.]
 
Thanks Duane,

I'll give the temporary table suggestion a try tomorrow at work. I'm still
puzzled as to why this occurs only when printing the report - why not when I
open it in print preview?

Rob


Duane Hookom said:
If your record sources and row sources are too complex, then you need to
simplify them. It's difficult to suggest any changes to your SQL
statements without seeing them.

At times you my just create temporary tables prior to opening the report.
This removes most of the complexity and your reports will render much more
quickly.]

--
Duane Hookom
MS Access MVP


Rob Parker said:
I have a report, containing three subreports, two of which contain chart
objects. This report opens fine (although rather slowly - the underlying
queries are quite complex) in preview mode, but when I try to print it I
get
an error message "Cannot open any more databases"; when I click OK to
dismiss this message, I immediately get another error message "An error
occurred while sending data to the OLE server (the application used to
create the object)." The report then prints, but is missing the chart on
the second subreport (and an additional blank page appears after that
subreport). The chart on the third subreport prints OK.

If I open the offending subreport directly I am able to print it with no
errors occurring.

The second error message has several suggestions, as follows:
* You may have tried to send too much data. If you're creating a chart
and
the chart is based on a query, modify the query so that it selects less
data. If the chart is based on a table, consider basing it on a query
instead so that you can limit the data.
* You may be using an OLE server that doesn't accept the clipboard
format.
* You may not be able to start the OLE server because it's not properly
registered. reinstall it to register it.
* Your computer may be low on memory. Close other application windows to
free up memory.

None of these seems applicable. The chart on the second subreport is
less
complicated than the chart on the third subreport (4 data series each
with
12 points plotted against one y-axis, compared to 6 data series each with
12
points plotted against two y-axes). The OLE server certainly works,
since
the subreport prints with its chart when printed alone, and the chart on
the
third subreport prints OK. The error occurs on two systems, both of
which
are running Windows XP Pro (fully up-to-date with service packs), and
which
have 2GB RAM. Closing all other applications does not affect the
problem. Both systems are running Access 2003, fully patched with all
service packs and hotfixes.

Any suggestions on why this is occurring and how to fix it will be
gratefully received.

TIA,

Rob
Click to expand...
Click to expand...
 
Hi Duane,

Removing the query from the rowsource of the chart and replacing it with a
temporary table (populated by code from the old query) has fixed my problem.

Thanks again for the suggestion,

Rob


Rob said:
Thanks Duane,

I'll give the temporary table suggestion a try tomorrow at work. I'm
still puzzled as to why this occurs only when printing the report -
why not when I open it in print preview?

Rob


Duane Hookom said:
If your record sources and row sources are too complex, then you
need to simplify them. It's difficult to suggest any changes to your
SQL statements without seeing them.

At times you my just create temporary tables prior to opening the
report. This removes most of the complexity and your reports will
render much more quickly.]

--
Duane Hookom
MS Access MVP


Rob Parker said:
I have a report, containing three subreports, two of which contain
chart objects. This report opens fine (although rather slowly -
the underlying queries are quite complex) in preview mode, but when
I try to print it I get
an error message "Cannot open any more databases"; when I click OK
to dismiss this message, I immediately get another error message
"An error occurred while sending data to the OLE server (the
application used to create the object)." The report then prints,
but is missing the chart on the second subreport (and an additional
blank page appears after that subreport). The chart on the third
subreport prints OK. If I open the offending subreport directly I am
able to print it
with no errors occurring.

The second error message has several suggestions, as follows:
* You may have tried to send too much data. If you're creating a
chart and
the chart is based on a query, modify the query so that it selects
less data. If the chart is based on a table, consider basing it on
a query instead so that you can limit the data.
* You may be using an OLE server that doesn't accept the clipboard
format.
* You may not be able to start the OLE server because it's not
properly registered. reinstall it to register it.
* Your computer may be low on memory. Close other application
windows to free up memory.

None of these seems applicable. The chart on the second subreport
is less
complicated than the chart on the third subreport (4 data series
each with
12 points plotted against one y-axis, compared to 6 data series
each with 12
points plotted against two y-axes). The OLE server certainly works,
since
the subreport prints with its chart when printed alone, and the
chart on the
third subreport prints OK. The error occurs on two systems, both of
which
are running Windows XP Pro (fully up-to-date with service packs),
and which
have 2GB RAM. Closing all other applications does not affect the
problem. Both systems are running Access 2003, fully patched with
all service packs and hotfixes.

Any suggestions on why this is occurring and how to fix it will be
gratefully received.

TIA,

Rob
Click to expand...
Click to expand...
Click to expand...
 
Back
Top