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

[jvbeaupre]

I just switched to the new Mac (M1 iMac 24", running the latest system) and updated excell to the most recent version 16.54.
Most of my code no longer runs.
It's mystifying that something so simple as the following bombs with an overrun 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
End Sub

Function diGammad(x)
diGammad = x
End Function

[Paul_Hossler]

Win 10, Office 365

All I did was use Option Explicit and Dim z1 as a Double

Possibly (bold, underlined) not Dim-ing it on a Mac it'd be a variant and that might cause an issue

Capture.JPG

Option Explicit


Sub a_test_digammad()
    Dim z1 As Double


    For z1 = 1 To 4.01 Step 0.1
        Debug.Print z1, diGammad(z1)
    Next z1
End Sub


Function diGammad(x)
    diGammad = x
End Function

[jvbeaupre]

That's encouraging.
I'll try that

[jvbeaupre]

That's encouraging.
I'll try that

I did try that, but the same problem occurs.
The problem seems deeper and related to 32-bit vs 64-bit implementations of VBA7.
(https://docs.microsoft.com/en-us/off...tions-overview)
I read the above reference think it's related, but I really don't know how to proceed.

I'd be very interested in hearing from Mac M1 users of Excel VBA.

Thanks,
Jim

[jvbeaupre]

UPDATE: The problem doesn't occur when I step through the code {CMD SHFT I}. That being said, that's not a solution, only a clue.

[georgiboy]

Have you tried to dim z1 as a variant instead of a double in the same code?

[jvbeaupre]

Have you tried to dim z1 as a variant instead of a double in the same code?

I've tried option explicit, variant, double and various combinations. The result is the same Runtime error 6 at the end of the z1 loop.

[jvbeaupre]

More info:
The problem occurs when there is a debug.print statement in a loop

[jvbeaupre]

It also occurs when debug.print is in NOT in a loop, but not always.

[jvbeaupre]

Problem is fixed in Excel 16.57