Trouble switching to the M1 Mac or Excel in Office16.56

Question

Trouble switching to the M1 Mac or Excel in Office16.56

I just switched to the new Mac (M1 iMac 24", running the latest system) and updated excel to the most recent version 16.56.

Most of my Visual Basic for Applications (VBA) code no longer runs.

It's mystifying that something so simple as the below code bombs with an overrun (Runtime error 6) at the end of the loop.

Has anyone else experienced similar difficulties?

Sub a_test_digammad()
   
    For z1 = 1 To 4.01 Step 0.1
    Debug.Print z1, diGammad(z1)
    Debug.Print "---"
    Next z1  'BOMB LOCATION
End Sub

Function diGammad(x)
diGammad = x
End Function

iMac Line (2012 and Later)

Posted on Dec 23, 2021 4:10 AM

Reply

Answer 1

Dec 23, 2021 9:05 AM in response to Jim from huntsville

I see the issue on my M1 MBP with Big Sur.

It is a problem with non-integer steps. Integer steps work fine.

Reply

Answer 2

Jan 23, 2022 12:12 PM in response to Jim from huntsville

Problem seems to be fixed in Excel 16.57.

Reply

Answer 3

Dec 30, 2021 2:39 PM in response to Keith Barkley

What I've learned so far:

The overrun error is associated with "debug.print".

It seems to always (or nearly so) happen when the "debug.print" is in a For-Next or Do loop.
It may happen when "debug.print" not in a loop.
Typically the printing occurs and the error is flagged by the debugger on the following statement.
Error is indifferent to Rosetta2
Context: M1 iMac 24", Monterey 12.1, Excel 16.56

Reply