Link to home
Start Free TrialLog in
Avatar of valmatic
valmaticFlag for United States of America

asked on

Send mail commands in Access VBA no longer work with Outlook 365. Mixed Outlook versions

Hi.  I've been bringing along an old, shared access database that was designed in Access 2000.  There are email send object and OLMail commands sprinkled throughout this thing.  Quite a few years back we moved to office (& Outlook) 2010 and I was able to keep it and all of the email functions working.  Recently, we are starting to move to Office 365 and are in sort of a hybrid state right now.. I have users running Office 2010 (w/Access 2010) and Outlook 2010, other users running office 2010 (& Access 2010) and Outlook 365 and a very few running the full Office 365 suite.   Besides that, I have users on both Windows 7 and on Windows 10.  Luckily, for now; the handful on the full office 365 suite don't use Access but I imagine we'll be moving more users soon.  I expect we'll be slowly moving users to full office 365 over the next couple years due to the number of users and lack of $$ available for this project.

My problem is in sending mail from within Access.  Everything else works fine.  My office and outlook 2010 users don't have an issue as long as the correct outlook object reference is available.  I think my issue is with the users who are using outlook 365.  The send object and OLMail objects don't work.  If I look at the references on various clients, I do see the correct MS Outlook Object Library reference for 14 or 16 based on the outlook client installed on that machine.  I've included my reference lists and a couple email send code examples being used.   What is my best course of action at this point?  I'm trying to steer away from a full redesign if possible..  thanks

' VBA1 OLMailItem Send Mail  (Error:  Run Time Error 5:  Invalid procedure call or argument)
Private Sub RGReason_LostFocus()
If RGReason = "Lost in Shipment" Then
    'Dim Outlook
    Set Outlook = CreateObject("Outlook.Application")
    Dim Message 'As Outlook.MailItem
    Set Message = Outlook.CreateItem(olMailItem)
    With Message
    .Subject = "RG #" & [RGNo] & " created for items lost in shipment."
    .Body = "Gina, please send a copy of Invoice #" & [InvNo] & " to Shawn for Lost Goods.  Thank you."
    .recipients.Add ("")
    .recipients.Add ("")
    End With
    MsgBox "Notice of Lost Goods has been issued to UserA and UserB to follow up with the carrier in recovering these goods.", , "Note"
End If
End Sub

Open in new window

'VBA2 SendObject example    (Error:  The Command or action 'SendObject' isn't available now.)
 Dim stDocName As String
stDocName = "CreditMockUp3"
DoCmd.SendObject acReport, stDocName, acFormatPDF, "", , , "Issue Credit for RG No. " & [RGNo], "Credit mock-up attached. See RG# " & [RGNo] & " for more details.  " 

Open in new window

Avatar of Daniel Pineault
Daniel Pineault

Do the users with the issue have outlook installed, configured and fully functional?  They can send/receive e-mails using Outlook?
Avatar of valmatic


Hi Daniel,  Yes,  all users can send and receive email via their Outlook client.
I don't believe you can automate the web versions of Office apps.  Is Outlook INSTALLED on the problem PC?  NOT the web app but OUTLOOK itself.
It must be installed, otherwise you would not have the typelib registered and the reference available in VBA.

Do you get any additional error info besides what you've indicated?

Also, check the application and security event logs for any related errors.

Hi Jim, Sorry so slow to respond.  
Yes, we have the full outlook client on each machine.  Nothing related in logs.  I also cleared my event logs to separate the chaff and nothing new that is related to my issue.  I just get an access message when it hits my send mail code:  "The command or action 'SendObject' isn't available now."  

That said,  another user who is running Windows 10, Office (w/Access) 2010 and outlook 2010 is having trouble with e-mail as well.  Only an issue in the OLMail functions though.  The other sendObject functions seems to work fine for him.  

Is there a better way to handle the emailing from Access that would work better with the various outlook versions?  I know Office 365 can also be tricky because it blows away some of the security settings on every update.  I'm looking into the security aspect but no luck so far.  

Avatar of John Tsioumpris
John Tsioumpris
Flag of Greece image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
There's also BLAT, which comes in a dll or command line, and for a commercial product,  FMS's Total Access Emailer

as far as vbSendMail, I've used it for years without issue.   CDO has been depreciated, but still works.

That aside, this is probably the MAPI bug that was recently introduced, for which I don't think there is any work around for currently.

 Let me double check some of the details on that.

For the users where this is not working, check the outlook version currently installed.   It started with Version 1811 Build 11029.20079.

Did some checking and Microsoft is still investigating this.   Your only choice is to either:

a. roll back the Office update on the effected machines.

b. Use some other means to send e-mails, which John and I commented on.


Note that this is not an issue if you are using Access 365, but only if you have Office 365 installed, but are using an older version of Access.
Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks all for your input on this.  I'm going to try changing my email object coding 1st and see where that takes me.  No budget for more office365 builds yet but sounds like that request needs to go up the chain...

I'm an old user of this site but have no idea how points are split anymore, if at all, so hope it comes out fairly..
We've moved to a process where questions are no longer closed and points are assigned based on you (and others) clicking on "This is the solution" and "This is helpful"


I realize that I was simply supporting your diagnosis with an official quote from Microsoft.  Sadly, no forward movement on this issue in nearly a month.