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-03-10T09:03:23+00:00

    Wow, Alex, these are very interesting findings. So they didn't fix the issue in Office 365 after all, they just made it less severe.

    Does anyone reading this have a *Premier* MS Support contract and wants to open a case with MS? (As we all know, "Professional Support" is useless for getting bugs fixed.)

    Best regards

    Heinrich

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-03-08T12:20:59+00:00

    March 7, 2017, update for Access 2016 (KB3128054)

    https://support.microsoft.com/en-us/help/3128054/march-7-2017-update-for-access-2016-kb3128054

    unfortunately not the fix for the bug discussed in this thread.

    so we have to wait .... and wait .... and wait.

    so sad.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-03-04T12:41:35+00:00

    after several days of intense testing we can confirm that our app crashes with runtime 2016.

    with runtime 2010 it is not crashing.

    we have many customers running our access application on access runtime 2016.

    so sad that there is still no fix for the runtime 2016.

    dear sirs at Microsoft - please fix this problem and publish an update for runtime 2016.

    thank you very much.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-02-14T13:45:55+00:00

    Houston we've had a problem !!

    Why is it taking so long from Microsoft to fix the problem ??

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-01-13T19:46:42+00:00

    We've confirmed the crashes continue even on the latest 365 BUILD 1611. MS please fix this or at least propose a workaround solution.

    Was this answer helpful?

    0 comments