A family of Microsoft relational database management systems designed for ease of use.
I have also had this problem. It is very obscure, but repeatable.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
I have also had this problem. It is very obscure, but repeatable.
I - and many of my customers have exactly the same problem too.
This behavior occured since Office 2016/Access 2016 has been deployed. Before (with Office 2013/Access 2013) everything was fine, after upgrade to Office 2016/Access 2016 this behavior occur.
If you have Office 2016/Access 2016 and you also install the Access 2013 Runtime, and open your application with the Access 2013 Runtime, everything works perfect.
There must be a bug in Access 2016. I hope somebody of Microsoft will listen to this conversation - and solve the problem!
Hi Alex,
Thank you for your reply,
For me SSRS sounds like "Let's go Goran sit back and spend another few months in changing and testing the application, explain to hundreds of users why they can't have their reports the way they used to, update all of them successfully, change user manuals, website, legal agreements and so and so..". If Microsoft want to cover the expenses and loss I would consider the other solution.
Otherwise, I am asking Microsoft to give us at least explanation what is going on...!!!
Any idea how to solve the issue would be also greatly appreciated...
Thank you in advance
I did some additional testing;
Version: Access 2016 - 16.0.6769.2017
Private Sub Form_Timer()
Dim strFile As String
strFile = "C:\Temp\A2016PDF-test\PDFs" & Format(Now, "hhmmss") & ".pdf"
DoCmd.OutputTo acOutputReport, "Areport", acFormatPDF, strFile, True, , , acExportQualityPrint
End Sub
Save as test.accdb
and compile as test.accde
open test.accdb
> after 10 minutes PDF is created
open test.accde
> after 10 minutes PDF is created
rename test.accdb to test.accdr
> after 10 minutes Access crashes
rename test.accde to test.accdr
> after 10 minutes Access crashes
Do the same with timerintervall 15000
> every 15 seconds a PDF is created without Problems
So the Problem seems to be, if Access idles for several minutes.
Thank you successcontrol.
So, let me see if I understand correctly. In the first case, the ten minute idle is too much, provided the extension is .accdr, which extension means that the access runtime engine is employed, even though you have the full version of access2016 installed.
In the second case, repeated short term idling (15 seconds) does not prevent the pdf from being stored. This is so no matter the extension, I gather. Very good. [Too bad we cannot rely on our users to never allow the app to go idle!!!]
Though I do not name my access file with an .accdr extension, I still experience the problem. My file is named with an accdb extension. However, since my application is launched from the command line as follows:
START "" "C:\Program Files (x86)\Microsoft Office\Office16\MSACCESS.EXE" /runtime "C:\Temp\FOO-APPS.accdb"
I am effectively causing the access runtime to kick in, I figure -- please see my /runtime flag.
This is good work you are doing.
Thank you for contributing your time and insight.