OnReport (PDF) Runtime error when report gets more than 3 pages long

  • Thread starter Thread starter Karen Creacy via AccessMonster.com
  • Start date Start date
K

Karen Creacy via AccessMonster.com

I get an OnReport runtime error...unable to trap it because none of the
events in the report are called (open, init, error...) nor the error
handling in the procedure...when this runtime error is thrown. We actually
take a report, copy it so that it can be renamed, then docmd.OpenReport
with the new copy. When the report gets to a certain length...it will
start getting an error that it cannot recover from. The call never makes
it out of the OnReport call.

I can then get behind the scenes...and see where the 'copied' report has
been created...open it in Access...and print to my Distiller printer
without any problems. It is just when it is running via the
DoCmd.OpenReport command that it fails out.
I am running Access 2000 - SP3....

When in runtime...it throws exception - runtime error and ends. When in
debug mode...never returns from the call.

Thanks for anyone's help...
 
How are you passing the filename to Distiller?

I create pdfs all day every day from Access, been running about 5 years.

Not sure I understand why you are copying the report either.

Maybe I can help if you give me details,
Mark
RPT Software
http://www.rptsoftware.com

email at the support email from my site if you need to
 
The name of the report..and ultimately the filename is generated 'on-the-
fly'. We do this by copying the report to the new name..then opening the
report/printing/saving...then deleting the copied object from Access Report
list when we are done.

This has been working pretty well for a while...just that we added another
type of report (old report that worked fine as normal report..but saving as
PDF new feature)..that is a little longer then others. It is hard to tell
what the 'real' problem is because when you are in the debugger...it never
comes out of the OpenReport command. In addition, breakpoints set in any
of the report events (init, open...etc) are not reached.

Adding error handling is ignored as well...it really has been hard to try
and nail down. I am in the process currently of manipulating the dataset
to see if it makes a difference.
 
One more clarification...

The report is configured to use the Acrobat Distiller printer as a default.
It has a port defined to point to a pre-defined location on the users's
system. The problem is consistent and can be reproduced on any system
where the software has been installed/configured. In addition, all users
are running on 'pre-packaged' OS images..with Accesss 2000 SP3 runtimes.
 
Back
Top