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
    2017-03-17T02:09:15+00:00

    Milestone achieved! Thanks a lot.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-04-14T18:06:30+00:00

    Hello,

    I wanted to let you all know that we are taking a look at addressing this issue.  Please see the request on our UserVoice site: https://access.uservoice.com/forums/319956-access-desktop-application/suggestions/11678409-docmd-outputto-acoutputreport-acformatpdf-c

    Mike

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-04-27T03:10:55+00:00

    Thanks a lot in advance.

    May this issue soon be solved with a Access 2016 runtime update.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-05-03T14:43:50+00:00

    When i read about this 8 minute issue, i thought this is a joke.

    but then i stopped time on my application. and gues what:

    8 Minutes and it crashes.

    1st: that is some of the more weird bugs (not the most weird) i have ever seen

    2nd:

    More than one year this is a known issue?

    Seriously Microsoft, how can you waste so much time without solving this bug?

    If the source would be public available, someone could fix it.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-05-03T17:05:52+00:00

    Thank you assembler_x64 for running the test that you did and posting your findings. 

    I agree, an 8 minute threshold makes it a "weird bug".  But, it is weirder still in that, if you have the Office365 version of Access2016, the threshold is 80 minutes!

    From my March 9th, 2017 post:

    "Happens for Office365 version of Access2016 as well as MSI Volume License of Access2016.  However, the "time limit" required for a crash to occur differs!  8 minutes for MSI, 80 minutes for Office365.  Yes, the crash threshold differs by a factor of 10! "

    I do hope Microsoft fixes this bug.

    Alex_891

    Was this answer helpful?

    0 comments