Error reproting dialogue

[Guest]

Hi,

I have an Access app that reports to individual pdf files (one pdf per
record). This all works (mostly). After about 500 to 700 pdfs it crashes and
prompts to send an error report to microsoft. I suspect this is an access
problem as I have tried this with three different pdf creation apps. I have
coded the app so that it will restart from where it crashed and continue to
create the pdfs. The problem is I have now have to create 35000 pdfs.

Is there any way to automatically answer the error reporting dialogue - the
"Do you want to send an error report to microsoft" message?????? If I can
trap this dialogue or bypass it the mdb will go through it's repair and
compact and restart creating pdfs without user intervention.

I am using Win 2000 SP4 (can't find any way to turn off error reporting)
Access 2002 SP3

It is propbably the wrong attitude but I am past caring whether the crash
can be fixed I just want to keep it going.

Any suggestions on automatically answering the error report dialogue,
stopping the dialogue or trapping the dialogue and coding a response........


Thanks for your time reading this .......... and (hopefully) your response.


Terry C

 

[John Nurick]

Hi Terry,

Have you debugged and tested your code to make sure that nothing there
could be causing the problem (e.g. if you're creating an object in the
process of making a PDF and not destroying it afterwards)? that's the
first place I'd look - and in my experience it's more likely than a bug
in Access itself.

Also, you say three different PDF creation apps. How different are they?
Many low-cost PDF-writers use the open-source Ghostscript engine, and
you could conceivably have exposed a problem in that. (Especially if
when using different PDF software on the exact same data set, your code
crashes after different numbers of reports.)

Meanwhile, to avoid the problem with the error-reporting dialog, why not
set the app to create a safe number (400?) of PDFs before restarting to
do the next 400.

 

[Guest]

Thanks John

I have used Adobe acrobat 6.1, PDF4U and another one (the name of which
eludes me right now).

Your suggestion about destroying the object may be right on the money. As a
self taught "coder" I am prone to doing some stupid things at times. I was
setting my pdf object to nothing but that was after the loop to create the
pdfs. I am now destroying it each time it creates a pdf. Currently testing.
At about 10-12 pdfs per minute it will take a while.

I will post an update as testing progresses.


Once again thanks very much for your response,

Terry C

 

[Guest]

Update

Still crashing after I destroyed the pdf object each time.

Going to try restarting the whole process after each 200 records.

The saga continues ........ stay tuned for the next installment.

In the mean time any suggestions greatly appreciated.

Thanks,

Terry

 

[Guest]

Dear All,

I finally found a way around my problems. A different approach. I change the
report name (in Access) to the name I want the pdf file for the record to
have. Print the report to the pdf printer (Adobe Acrobat in this case) and
filter out all other records. Move to the next record change the report name,
change the filter and so on. Adobe saves the output pdf with the report name
and that's why the report name needs changing.

Works much faster and hasn't crashed yet ........ testing is up to 8000
records at a time so far.

Thanks

Terry