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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2016-09-14T21:15:07+00:00

    Hi Alex!

    I'm afraid this has nothing to do with Windows 10 LTSB but rather with the fact that you are probably using a Volume Licence version of Office 2016 - which is MSI-based. The retail versions and the Office 365 versions are Click-to-Run (C2R) based.

    Both versions differ in patch level: Office 2016 MSI is currently at 16.0.4432.100 and Office 2016 C2R is at 16.0.7167.2040.

    Unfortunately, there is currently no way to get Office 2016 MSI to a higher patch level.

    Best regards

    Heinzi

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2016-09-14T19:58:01+00:00

    Hi Heinzi,

    To date, I am unable to upgrade Access2016 to 16.0.7167.2040 or higher, so I cannot test to see whether the app crash problem has gone away. 

    My coworker and I think my inability to upgrade is because I am running Windows10 Enterprise, LTSB (Long Term Service Branch), and there are thus some limitations in how far I can upgrade Office2016.  At present, I can only upgrade Office2016 to 16.0.4432.1000.  At this upgrade level, the 'report to stored pdf' app crash problem still exists.

    I am soon having my computer rebuilt with Windows10 Enterprise, Current Branch -- that is, not LTSB.  After I do, I will install Office2016 and hopefully be able to upgrade Office to  16.0.7167.2040 or higher.  I will then test to see whether the app crash problem has gone away.   In any case, I  will report my findings, good or bad.

    Alex

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-09-09T18:49:46+00:00

    Hi Heinzi,

    Thank you so much for replying.  I really appreciate your reporting on a fix in Access 2016 Version 16.0.7167.2040 or higher.  You have done me and many other people a service for reporting on this.

    In my post of March 29th, 2016, I didn't mention the version number of Access 2016 Pro Plus I was using!  Such an oversight.  I didn't bother even to record the version in my test notes.  I confess to not have checked for it.

    Today, September 9th, 2016, I  checked my Access version number and it is 16.0.4405.1000.  Was it 16.0.4405.1000 on March 29th, I do not know.  However, the problem I reported on March 29th 2016 still exists.  If 480 seconds or more, there is an app crash upon attempt to save pdf of a report to a folder!  If less than 480 seconds, no app crash!

    I am thus in a perfect position to upgrade to 16.0.7167.2040 and show the problem has gone away, just as you have indicated.  Unfortunately, I need to confer with others in my group to figure out the best way to auto-update MS Access.  I do not have the "Update Now" button available to me in the installed, retail version I am using!

    I hope by end of next week to be upgraded to 16.0.7167.2040, and at that time, I will retest.  I will report back my findings.

    Thanks again.

    Alex

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-09-09T14:31:01+00:00

    Apparently, the problem has (silently) been fixed by Microsoft.

    I can reproduce the issue with Access 2016 Version 16.0.4266.1003.

    I can no longer reproduce the issue with Access 2016 Version 16.0.7167.2040 or higher.

    Best regards, hth

    Heinzi

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-08-02T18:11:42+00:00

    I apologize for giving you the impression that a "work around" of this size is reasonable.  It is not!

    For the company I work at, SSRS is part of our Calendar Year 2020 plan for reporting,  so I decided to move in that direction now.... rather than wait on Microsoft to fix what I think can be called a bug. 

    I spent a few hundred hours of my time making a switchover to SSRS for reporting. This wasn't just time spent making reports in SSRS.  It was time spent making a piece of middleware between my access applications and our SSRS server to handle requests --- for the case where there is one template, that is run with differing parameter values.  We haven't Sql Server Enterprise, so I had to build middleware for something SSRS Enterprise can do.

    As far as time requirements are concerned:  I only converted two of the perhaps 300 reports I have to

    SSRS.   I converted only the reports that were likely to be effected by the "8 minute" problem.

    Like you, I really would like a solution from Microsoft. 

    I simply felt I couldn't wait. 

    I appreciate your taking the time to share your experience and pain. 

    If others do, perhaps Microsoft will take notice.

    Was this answer helpful?

    0 comments