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-01-12T16:18:40+00:00

    There is a post earlier in the thread about msi installers.

    The MSI installer is currently at an earlier version than 365 installer - hence it causes the issue in both msi and runtime vesions.

    The issue also occurs in the latest 365 release if the files is opened as any other format than accdb i.e. accdr, accde etc.

    I have seen no official release from Microsoft when this issue is going to be permanently fixed.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-01-11T19:40:21+00:00

    I wanted to bump this thread as I am having the exact same issue. My app will convert a report to PDF using DoCmd.OutputTo consistently for up to 8 minutes and then any length of time of having the app open past 8 minutes results in a crash 100% of the time. I have tried a few different reports but it makes no difference.

    We are running an MSI volume license copy of Access on version 16.0.4266.1001 32-bit and there have been no other updates available.

    I tried the app running in Access Runtime 2013 and the crash does not occur. This is not feasible because our end users get a "configuring Microsoft Access to run for the first time" every single time they launch an app if we have Access Runtime 2013 installed on the same server as Access 2016 so I had to uninstall 2013.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-11-13T09:36:09+00:00

    Yep, that's exactly what our customers love to hear:

    "Thanks for buying our Access-based ERP system and rolling it out on your 50 workstations. Oh, and by the way, you might have to wait a few months for it to work reliably without crashing. No, we can't tell you how long, just keep your fingers crossed. You don't mind, do you?"

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-11-13T08:41:29+00:00

    You might need to wait for another update of MS Access 2016 and hope that it will fix the issue.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-11-10T15:46:50+00:00

    I appreciate that you are trying to help, but digging through MS forum threads with all their noise is hard enough already. Adding random links without being sure that they help doesn't make it better in my opinion.

    Best regards

    Heinzi

    Was this answer helpful?

    0 comments