Home

Access unable to send email via Outlook since upgrade to 2016

%3CLINGO-SUB%20id%3D%22lingo-sub-171205%22%20slang%3D%22en-US%22%3EAccess%20unable%20to%20send%20email%20via%20Outlook%20since%20upgrade%20to%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-171205%22%20slang%3D%22en-US%22%3E%3CP%3EHI%20all%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20hoping%20someone%20can%20help.%26nbsp%3B%20I%20have%20developed%20an%20Access%20db%20for%20a%20small%20non-profit%20(designed%20in%20Access%202013)%2C%20and%20as%20a%20small%20part%20of%20it's%20functionality%20I%20needed%20to%20send%20an%20email%20via%20the%20'EMailDatabaseObject'%20macro%2C%20which%20was%20working%20fine.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERecently%2C%20one%20of%20our%20employees%20received%20a%20new%20computer%20with%20Windows%2010%20and%20Office%202016%2C%20and%20now%20this%20function%20breaks%20the%20macro%2C%20with%20a%20%22Microsoft%20Access%20cannot%20send%20this%20e-mail%20message.%22%20error.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20a%20hunch%20that%20this%20is%20some%20new%20bit%20of%20security%20set%20by%20default%20by%20Microsoft%2C%20but%20the%20only%20hints%20towards%20that%20have%20suggested%20that%20I%20need%20to%20edit%20the%20registry%20for%20a%20fix.%26nbsp%3B%20I%20am%20hoping%20that%20there%20is%20a%20simple%20workaround%2C%20and%20would%20welcome%20any%20feedback.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20in%20advance%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAndrew%20Bethke%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-175624%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20unable%20to%20send%20email%20via%20Outlook%20since%20upgrade%20to%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-175624%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20this%20new%20computer%20come%20with%20Office%20365%20pre-installed%3F%26nbsp%3B%20If%20it%20did%2C%20you%20could%20be%20looking%20at%20the%20%22Store%20Version%22%20of%20the%20Office%20suite%20which%20comes%20installed%20as%20a%20Windows%2010%20App.%26nbsp%3B%20Because%20it%20has%20several%20different%20operating%20paths%2C%20this%20version%20tends%20to%20break%20things%20like%20macros%20and%20third%20party%20add-ins.%26nbsp%3B%20IF%20this%20fits%20your%20situation%2C%20the%20fix%20seems%20to%20be%20removing%20the%20Store%20version%20first%2C%20then%20installing%20either%20Click%20to%20Run%20or%20MSI%20versions.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Deleted
Not applicable

HI all,

 

I am hoping someone can help.  I have developed an Access db for a small non-profit (designed in Access 2013), and as a small part of it's functionality I needed to send an email via the 'EMailDatabaseObject' macro, which was working fine.

 

Recently, one of our employees received a new computer with Windows 10 and Office 2016, and now this function breaks the macro, with a "Microsoft Access cannot send this e-mail message." error.

 

I have a hunch that this is some new bit of security set by default by Microsoft, but the only hints towards that have suggested that I need to edit the registry for a fix.  I am hoping that there is a simple workaround, and would welcome any feedback.

 

Thanks in advance,

 

Andrew Bethke

1 Reply
Highlighted

Did this new computer come with Office 365 pre-installed?  If it did, you could be looking at the "Store Version" of the Office suite which comes installed as a Windows 10 App.  Because it has several different operating paths, this version tends to break things like macros and third party add-ins.  IF this fits your situation, the fix seems to be removing the Store version first, then installing either Click to Run or MSI versions.