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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-06-20T12:28:12+00:00

    CTR - MSI - I don't know what's what! I would have thought that Office 365 would update Access as required, but as at 15 June 2017, the full 2016 version was causing our routine to crash following printing to pdf issue summarised below.

    What I do know is that Heinzi was spot on - this fix worked for us.

    We were using the Access version that comes with Office 365. We have our back end on one of our PCs and that PC and two others have .accdr front ends that we use to run the business. Printing to .pdf stopped working. Initially this seemed random, but we, along with others, discovered that after 80 minutes, printing to pdf resulted in the application closing down. Subsequent prints were fine but if we didn't try printing to pdf for another 80 minutes, the application closed down again.

    Taking Heinzi's advice, we installed 2013 Runtime and set up a link forcing our .accdrs to open im 2013 Runtime. That's sorted the issue for us.

    I'd love to know whether or not the 2016 Office 365 version has been fixed, but I dodn't fancy faffing around trying to find out, now that we have a fix...

    Thanks, Heinzi.

    Pete

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-06-19T11:08:58+00:00

    Indeed. Unfortunately, it leaves all the questions actually required to deploy the fix to your customers unanswered, like:

    * Access 2016 CTR (= Office 2016 Retail and Office 365): In which (build) version of Office 2016 CTR has the bug been fixed?

    * Access 2016 MSI (= Office 2016 Volume License): Where can the fix for this issue be downloaded?

    * Access 2016 Stand-alone Runtime: Where can the fix for this issue be downloaded?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-06-19T10:34:53+00:00

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-06-16T00:21:04+00:00

    can't find any KB for the mentioned bug fix........

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-06-09T17:58:12+00:00

    Heinzi - I had an email saying that the MS Office team had fixed this:

    Bug fix is rolling out to customers.

    Please upgrade to the latest Office version to see it,

    Michal [MSFT]

    I got excited and deleted Access 2013 runtime before testing your suggested workaround, thinking that the fix would automatically update onto our Office 365 Access 2016 versions, but it's not fixed. I'll go back to trying your Office 2013 workaround as above. I can't see how to update Office 365 Access 201 to the latest version...

    Was this answer helpful?

    0 comments