DoCmd.SendObject problem

[mor10]

I have recently noticed that sending an email, using DoCmd.SendObject, from Access 2010 runtime to Outlook 2016, causes Access 2010 runtime (and full version as well) to hang after the message is sent. It looks like control is never handed back after the message window closes. I have seen this at a customer site and also been able to reproduce the problem locally. The workaround I have found is to use Access 2016 runtime. Is there a solution where I can avoid using Access 2016?

My database does run fine in 2016, but I have not been able to find if there is a way to run the Package Solution Wizard in 2016. Has anybody got any experience with this problem?

 

[Ranman256]

How bout try using the
"Set obj = new outlook.application" method?
(Google this)

 

[GinaWhipp]

Aside from using Automation there really isn't one. There is also no Package Solution for Access 2016 (or Access 2013). There is an alternative, have a look at...

http://www.ssesetup.com/

 

[mor10]

How bout try using the
"Set obj = new outlook.application" method?
(Google this)

No, because not all my users use Outlook, so I must allow them to chose default email program.

I also do have a built in SMTP solution based on CDO, but since office365.com require TLS that CDO does not support, that is not an option for them either.

The funny thing is that both these two issues have surfaced in the last month or two. Previously there were no problems using SendObject from Access 2010 to Outlook 2016, and just a few weeks ago I am sure I was able to use port 25 and no TLS, to send emails using office365, but MS have either by accident, or on purpose, closed both these doors for me.

 

[Leo_Polla_Psemata]

I have recently noticed that sending an email, using DoCmd.SendObject, from Access 2010 runtime to Outlook 2016, causes Access 2010 runtime (and full version as well) to hang after the message is sent. It looks like control is never handed back after the message window closes. I have seen this at a customer site and also been able to reproduce the problem locally. The workaround I have found is to use Access 2016 runtime. Is there a solution where I can avoid using Access 2016?

My database does run fine in 2016, but I have not been able to find if there is a way to run the Package Solution Wizard in 2016. Has anybody got any experience with this problem?

Hi
I am going through huge troubles because of this problem.
Access 2010 docmd method doesn't work with outlook 2016 o365.
The whole access hangs.
I wonder what could be the effective remedy for this .

If I find another VBA code which composes and sends email through outlook 2016, another method outside docmd.sendobject, should I have the same problems ?

 

[GinaWhipp]

@Leo Polla Psemata,

Using Automation (with Late Binding) should solve your problem. If you are looking for some help in that area please consider starting a new question so it gets the attention it deserves.