Problem sharing Excel XLSM files with MACROS between WINDOWS and MAC (Spanish Office 2016)

Andres Rotman 1 Reputation point
2020-08-12T23:20:35.027+00:00

1) Create a new file XLSM with a MACRO inside name of module in spanish is automatically assigned as "Módulo 1"
2) Take the file, open it in WINDOWS EXCEL. you will see this:

17341-captura-de-pantalla-2020-08-12-a-las-194340.png

3) If you SAVE on windows side, the file becomes CORRUPT and you will not be able to open on MAC without loosing the MACROS

4) Workarround I used to solve is the following, on Windows I created a new Module, paste the code on it and delete the first Module with the "bad" name.

5) After that on MAC you will see the following:

17351-captura-de-pantalla-2020-08-12-a-las-194054.png

6) Even if you see it BAD, works in that way....

Is this a KNOWN BUG ? I have searched on internet and I did not find nothing reported..

Office Mac
Office Mac
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Mac: A family of Apple personal computers that run the macOS operating system.
471 questions
Excel Management
Excel Management
Excel: A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.Management: The act or process of organizing, handling, directing or controlling something.
1,656 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Emily Hua-MSFT 27,546 Reputation points
    2020-08-13T09:30:41.11+00:00

    Hi Andres Rotman,

    I can reproduce your issue, I create a .xlsm file with a macro via Office 2019 for Mac, when opening this file on Microsoft 365, the module's name changed as the following screenshot shown.
    17395-capture14.jpg

    I haven't found a solution yet, it's recommended to raise this issue in Excel app on Mac, click the Feedback icon at right upper right corner, then you may click I don't like something or I have a suggestion to submit this feedback. Thanks for your understanding.

    17407-capture15.jpg

    0 comments No comments