Access 2016 accde "DoCmd.OutputTo acOutputReport, , acFormatPDF..." crashes after 10 minutes

Anonymous
2016-01-24T09:19:56+00:00

Create PDF in accdb is no problem.

Create PDF in accde crashes after 10 minutes.

Command: DoCmd.OutputTo acOutputReport, , acFormatPDF, strOutputFile, False, , , acExportQualityPrint

At first the DoCmd.OutputTo method runs fine.

But if you do 10 minutes nothing (only opened) and then you try to run DoCmd.OutputTo again, access crashes without error.

It seems like a timer-problem, but there is no timer.

Only by acFormatPDF and only with accde. In a accdb-file all is fine.

It is not a problem of the PDF-Software. I checked several PDF-Software-Products. Additional: Parameter Autostart is false.

So the PDF-Software should do no matter.

It is not a Problem of anti-virus-Software. I checked it also without any anti-virus-Software.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

75 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2016-11-07T21:44:46+00:00

    Hi Heinzi,

    As of the moment Access 2016 latest update was last 8/23/2016. You can refer to this link to know more about the latest Microsoft product update releases.

    Regards.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-11-08T11:10:50+00:00

    Thank you. This list only contains entries for the full version of Access 2016, is there a similar one for Access 2016 Runtime?

    And does any of these updates fix the problem described in this thread? 

    Thanks, best regards

    Heinzi

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-11-08T17:40:02+00:00

    Hi Radney.

    This problem has not been resolved.  I am too busy on other projects to do any testing to confirm whether some patch trickled in for the Volume License version.   See my Sept 20, 2016 entry where I indicate the problem is not resolved.

    Others are mentioning the need for a patch applied to the runtime version of MS Access. 

    I do not think this problem is resolved.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-11-09T15:22:25+00:00

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-11-09T17:42:29+00:00

    Hi Fukiko,

    I went out to the article you provided a link to.  Did someone in the link solve the problem?   If so, could you kindly tell me the date of the post that has the solution present? 

    Thank you so much for taking the time to respond.

    Alex

    Was this answer helpful?

    0 comments