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-09-14T22:38:34+00:00

    Thank you Heinzi.   I appreciate your telling me about this. Our Office 2016 was purchased from a Volume License Center  vendor.  On the purchase order I see "OfficeProPlus 2016 SNGL MVL") -- we bought one copy to test.  I may have referred to it as retail version, but perhaps shouldn't have.

    In any case, I suppose I will need to wait to get 16.0.7167.2040 or higher.   I am glad you wrote back.  I have called off upgrading my test box from Windows 10 LTSB to Current Branch as a consequence. Your writing back saves me and my coworker a lot of unnecessary work.

    Thank you.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2016-09-20T02:00:37+00:00

    Hi Alex,

    We're glad to know that your concern was resolved, other Community members may find this thread helpful. Feel free to post here at the Community if you have anymore concern.

    Regards.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-09-20T08:24:12+00:00

    Hi Radney!

    I'd say the issue is resolved as soon as the MSI (Volume License) version of Office 2016 gets patched as well. Since you are an MS employee, can you forward that request to the people in charge?

    Thanks, best regards

    Heinzi

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-09-20T19:03:22+00:00

    Hi Radney:

    Heinzi is correct.  The problem has been resolved for many kinds of Office 2016 users, but not all kinds. 

    At present, we are making use of an MSI (Volume License) version of Office 2016, and so the problem is not yet resolved for us.

    I'd very much appreciate Microsoft patching the Volume License version as well.  Once Microsoft does, I will complete my testing to confirm the problem has gone away.  I will post to this page the result of my testing.

    Thank you,

    Alex R.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-09-21T13:15:19+00:00

    The Runtime version hasn't been updated yet either - at least I haven't found a way to update it.

    Has anyone found a Runtime Update?

    Was this answer helpful?

    0 comments