ActiveX backward compatiblity issues with 365 to 2010

[KendelSmith]

I am transitioning a set of interrelated Excel documents that use VBA code for lookups, data manipulation and calculations from Excel 2010 to Excel 365. I have both on my development machine, however these get sent (via email) to customers all over and then returned. I use .xlmb file formats for the file size savings however this doesn't seem to be affecting the outcome.


CURRENT ISSUE
When I save a workbook using 365 on my development machine, users get errors when performing an action that runs my VBA code when run from a machine that only has 2010 installed (if both versions are installed, the behavior does not seem to happen). I have focused the problem to when there is code in a module and there is an ActiveX control on a sheet. Only this combination seems to create the issue.


The test file/code I've created that consistently shows the issue is a workbook with the following code in a module:

Dim strBook As String
' Worksheet Names
Public Const wksTest = "Sheet1"


Public Function TestMe(PassedSheet As String)


    strBook = ActiveWorkbook.Name


    Workbooks(strBook).Worksheets(PassedSheet).Protect
    Workbooks(strBook).Worksheets(PassedSheet).Unprotect


    MsgBox "Worked from function", vbOKOnly, "Response"


End Function

And code in the sheet. It works with this code:

Private Sub Worksheet_SelectionChange(ByVal Target As Range)


    If Target.Row = 2 And Target.Column = 2 Then
    
        strBook = ActiveWorkbook.Name
        
        Me.Protect
        Me.Unprotect
        
        MsgBox "Worked from sheet", vbOKOnly, "Response"
        
        Call TestMe(wksTest)
    
    End If


End Sub

However if an ActiveX Command Button named "TestButton" is added to Sheet1 and this code is added:

Private Sub TestButton_Click()


    strBook = ActiveWorkbook.Name
    
    Me.Protect
    Me.Unprotect
    
    MsgBox "Worked from Button", vbOKOnly, "Response"
    
    Call TestMe(wksTest)


End Sub

The workbook will no longer function if saved from 365 and opened with 2010 on a machine with only 2010 installed.


I would love to get feedback on possible fixes for this issue.


Thanks

 

[KendelSmith]

Bumping to top. Anybody have any ideas/comments?

 

[MARK858]

Anything to do with the orange banner at the top of the page?

 

[KendelSmith]

Nope. I tested that first and it appears to be something entirely different (at least, the MicroSoft FixIt doesn't help and it only affects worksheets that have been saved using 365 and opened by 2010 with ActiveX and functions in a module ... very specific)