VBA code failing in older versions

[gordsky]

Hi All,

I use the below code without issue on the machines at work to generate emails from vba and paste various bits from spreadsheets into them. All but two of the machines are using Excel/Outlook 2016 or later and the code runs no problem on them

2 of the machines were swapped out and replaced with ones running 2013 versions of both and the code now fails on the line " signature = newEmail.htmlBody"
Can anybody tell me why or point me in the direction of a solution

Dim Outlook As Object, newEmail As Object
Dim signature As String

Set Outlook = CreateObject("Outlook.Application")
Set newEmail = Outlook.CreateItem(0)
Who = 'takes names from the spreadsheet


Set newEmail = Outlook.CreateItem(0)
                
            With newEmail
              
              .display
               signature = newEmail.htmlBody
              .To = Who
              
              .subject = ThisWorkbook.Name
              .ReadReceiptRequested = False
                        
               Application.CutCopyMode = False
              .Attachments.Add ThisWorkbook.FullName
    
            End With
End Sub

 

[RoryA]

What's the error? I suspect you're hitting the object model guard since htmlbody was one of the protected properties. Also not sure why you display the email before it's populated?

 

[gordsky]

RoryA thanks for your reply.

The error is shown as runtime 287 application-defined or object-defined error
I display before populating as I was advised that this was the only way to capture the individual signature of each user. Is that not correct?

 

[RoryA]

That does sound like the object model guard. Unfortunately, that wasn't that easy to work around - you need something like the redemption library, or vbMAPI.

 

[gordsky]

That does sound like the object model guard. Unfortunately, that wasn't that easy to work around - you need something like the redemption library, or vbMAPI.

so as a workaround if I remove the signature capture line would the rest of the code run or is the protection for the message body in its entirity.?
Is there a way to perhaps detect which version of excel/outlook is being used ?

 

[RoryA]

There's a list of all the secured properties/methods of each object here: Protected Properties and Methods

You could test if the Application.Version is less than 16

 

[gordsky]

There's a list of all the secured properties/methods of each object here: Protected Properties and Methods

You could test if the Application.Version is less than 16

RoryA thanks for your help. I take it these guards were removed for later versions hence the reason the code works on the other machines??

 

[RoryA]

Not removed, but they were changed as I recall so that they would recognise installed AV software and reduce security accordingly. They could also be turned off via Group Policy I think.

 

[gordsky]

RoryA thanks for your suggestions so far. Could the problem be an early / late binding issue.? I dont understand the difference exactly so is my code early or late

 

[RoryA]

No, I don’t think so. Yours is late bound.