The macro Workbook_Open() does not work on macOS

Originally Posted by Aromis

... on MacBooks older than 17 years old, when opening the file, the message "Invalid procedure call or argument" appears ...

Please Login or Register  to view this content.

In "old excels" (if there is one installed there and not a new one), the equivalent of the "Workbook_Open" event was the "Auto_Open" event (in win sys).
Unfortunately, I have no one reference to what it looked like in "Offices for Mac".
To open old excel files with the "Auto_Open" in new excel installations, we must use the "Workbook.RunAutoMacros" method (described in the contextual help of the VBA editor) however, this is not possible in the "opposite direction" - "nam nuzhno redaktirovat' makrosy".

Originally Posted by Aromis

Good day everyone!
There is a file (in the application) that, using macros, allows you to create authorization with different levels of access to different sheets of the book.

The essence of the problem is this: the file works fine on Windows, it also works on a MacBook up to 2017 inclusive in office 16. The selection of Macs is not very large, where I tried to open it, but on MacBooks older than 17 years old, when opening the file, the message "Invalid procedure call or argument" appears and Visual Basic opens with the red line highlighted in yellow below.

This code is written in ThisWorkBook.

Please Login or Register  to view this content.

Offices were 16 and 19. The names of all modules seemed to be written in Latin. Macros were enabled on all MacBooks. Has anyone encountered this problem, or can they help get it to run on any Mac? Thank you very much in advance for your advice))

For the default login, the login is Admin, the password is 1.

How about this

Please Login or Register  to view this content.

Originally Posted by zameel

How about this

Please Login or Register  to view this content.

Unfortunately it doesn’t work, when saving it VBA says a compilation error

UPD. The file works on Intel processors, but not on M2 processors. Is there any solution to this problem?

Originally Posted by rorya

I thought you said older Macs were the problem?

Sorry, apparently it looked incorrect. On old MacBooks everything works fine, but on new ones it doesn’t, especially with non-Intel processors.

Originally Posted by rorya

Making the changes I suggested worked for me with an M2 MacBook

Seriously? I renamed all the sheets to English, but the file still didn’t work... Can you attach to the message the file that worked for you?

Everything worked!) Thank you very much for your help! The topic can be closed