Access 2016 accde "DoCmd.OutputTo acOutputReport, , acFormatPDF..." crashes after 10 minutes

Anonymous

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.

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

Anonymous

2016-04-27T21:27:05+00:00

I'm sorry Robert. I suppose I didn't answer your question about runtime or full access. I am running my application in a full version of Access2016, that was a part of Office Pro Plus 2016 (32 bit), run on Windows10 (64bit) .

I am launching my accdb from a bat file using START and a /runtime flag... so perhaps it is sort of like using the runtime version of Access, though I actually have the full version.

Hope this helps,

Alex R.
Was this answer helpful?

0 comments No comments
Anonymous

2016-04-27T21:39:55+00:00

Hi Alex,

Yes, since I have replaced my Office 2007 and 2013 with Access 2013 all users who working with my application crash when trying to export to PDF (not always one time on two)

P.S Over 50 users have the same problem (windows 7 and Windows 10 too)

I have absolutely no idea about the solution and I find nothing about this problem on the Web...

Regards

Robert
Was this answer helpful?

0 comments No comments
Anonymous

2016-04-27T21:56:11+00:00

From my side, all applications have an .addr extension.

20 users work in terminal server environment with Access 2016 runtime 32 bits (Windows 2008 server R2) and the other users work locally with Access 2016 runtime 32 bits too and everybody have the same problem.

Probably I must uninstall runtime 2016 and reinstall 2013...

Thks

Robert Simard
Was this answer helpful?

0 comments No comments
Anonymous

2016-04-27T23:25:40+00:00

Robert. I do appreciate your getting back to me with more information on your particular situation.

It really annoys me that I cannot find anything in the Windows Event Log corresponding to the crash. As I mentioned in an earlier posting, I've considered reviewing ProcessMonitor logs, but am a bit overwhelmed by how many ProcessMonitor entries there are, even in the second in which the export to pdf goes from good to bad! 7min59 seconds good. 8min00 seconds bad!

I need to eventually transition all my reporting to SSRS, and so have decided to begin use of SSRS in response to this problem.

For you, your using Access2013, I gather, is a way to make the problem go away. This is good. I hope there is nothing preventing you from doing so.

I also haven't seen a solution on the web.

Good day,

Alex
Was this answer helpful?

0 comments No comments
Anonymous

2016-04-27T23:46:04+00:00

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!
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments