This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
A family of Microsoft relational database management systems designed for ease of use.
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.
For the MSI and stand-alone runtime, you can download the fix by using the following link
As for CTR, it was apparently released in April and should be included in the build 16.0.8114.1000 or higher. So ensure your installation performs an update.
Just to give everybody a heads up. Our company also discovered this problem with exporting to PDF in .accdr files and Access 2016. We went through the same troubleshooting steps as everybody else in this thread and discovered the issue was new in 2016 and the export process worked fine in Access 2010/2013. We created a test database from scratch to test not only the function, but also using the pdf export button in the Access 2016 ribbon. In both instances Access crashes after its been open a certain amount of time. As another posted indicated, the MSI and earlier click to run versions seem to crash much earlier while the more recent builds appear to crash after Access has been open between 1-2 hours.
We opened a paid support ticket with Microsoft Support and after going through several levels of support over the course of several weeks, the Office VBA Support team confirmed this is a bug and it will be fixed at some point in the future. The support fee we paid was refunded because it was a confirmed bug.
We were told an ETA could not be provided, but we were told it was confirmed to be a bug and was added to their database of bugs to fix.
Thank you Kirk. This is a very unusual bug. 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! Please read on.
Concerning MSI Volume License of Access2016 (16.0.4456.1003, tests done March 2017)
We consistently experience App Crash 100% of the time if the MSI Volume License copy of Access2016 has been open for 8 minutes or more when the command to 'store as pdf' is given. Please see my 29th March, 2016 posting for a description of how testing is done (Version 16.0.4456.1003, MSI Volume License). The calendar year 2016 testing was redone in March of 2017 with the same result. Please note that 7 minutes and 59 seconds is fine. No App crash. Pdf is stored fine.
Concerning Office365 Version of Access2016 (16.0.7341.2035, tests done March 2017).
We consistently experience App Crash 100% of the time if the Office365 version of Access2016 has been open for 80 minutes or more when the command to 'store as pdf' is given. Testing done in same way as described in my 29th March, 2016 posting. Please note that 79 minutes and 59 seconds if fine. No App crash. Pdf is stored fine. This is very repeatable. Three times, success when command given at 79 minutes and 59 seconds. Three times app crash when command given at 80 minutes and 00 seconds! Please note that I explored a time range from 20 seconds to 300 minutes, binary search style. 24 trials were run.
Question:
Why would there be an order of magnitude difference in the time threshold : 8 versus 80 minutes? I am puzzled!!!
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.
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