"New" Outlook

[Gasman]

MSFT is very much aware of this, and looking into which scenarios should be supported long-term.
DoCmd.SendObject is one of the areas of attention. It cannot just stop working.

In the little I have used Access with Outlook, I have always used Outlook Automation

 

[Minty]

I have a large system that we have recently taken over supporting and have moved to Azure BE. It uses Docmd.SendObject extensively, and I was looking to refactor it to use Outlook Automation instead as it's more customisable.

However, I may hold fire if it's not going to work long term, what's the point.
Shirley I'd be better of moving it all to CDO?

 

[Gasman]

My colleague told me today that he was able to go back to the normal outlook?
He was not impressed with the New Outlook.

 

[adhoustonj]

I've just encountered this with a database user as well.

From the Access Form once they click the command button to send the email, the outlook new message screen pops up with the attachment attached, and they click send, thinking everything is working as normal. Well today rolls around they found out the emails weren't being received, and upon further inspection, don't show in the SENT box either.

So I remote in and noticed the 'Try New Outlook' was toggled on.. Toggled it off, did a test email, it works, and then the previous emails all sent as well. I'll have to see if we can roll out the registry setting as group policy or something..

    Dim oApp As Object
    Dim oMail As Object
    Dim olMailItem As Object

    Set oApp = CreateObject("Outlook.application")

    Set oMail = oApp.CreateItem(0)
    oMail.Body = "Please review."
    oMail.Subject = "Notification"
    oMail.To = Me.txtEmail
    oMail.Attachments.Add "Y:\Me.T_ & ".xls"
    oMail.Display
    Set oMail = Nothing

 

[Gasman]

See code from @isladogs in post #10

 

[AngelSpeaks]

So glad I found this discussion. I wasted a lot of time trying to get Outlook to work with my new Access application. I'm using Access 2019.