Problem with SendObject in Access runtime 2010 with Outlook 2013

Question

Hi

I have an application that runs on Access 2010 runtime. In that application I use "DoCmd.SendObject" to send mail from the default mail client. I has worked fine with Outlook 2007 and 2010, but when I installed outlook 2013 it gave me this error "sendobject isn't available now".

Its like its trying to use Outlook 2010 instead of 2013. Any ideas on how to debug solve this.

Answer 1

Did you read my post? Access can't see later versions of Outlook. You have to use a work-around with MAPI calls. vbMAPI is the only simple solution I have found that does not require DLL registration.

Answer 2

Please don't piggyback your question on another thread. Use the Participate option and post your own question giving details.

Answer 3

I have the same problem, it gives me an error of runtime 4056

Answer 4

That's one big drawback when not using a version of Access that is equal to or higher than the rest of the suite. Use Access 2013 runtime or get www.EverythingAccess.com's VBMapi. I'm not connected with the company; I just know it worked for me when I had Access 2003 running on a computer where the rest of the suite was 2010. What it does is plunk some classes into your code that wraps the Outlook object so older versions of access can see it.

Answer 5

"Isn't available now"? That seems to indicate your app is in an unusual state where it could not do it.

Try this: open the Immediate window (Ctrl+G) and type in a simple DoCmd.SendObject statement. Does it send?