A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.
I agree with Jim that unless the code is posted, any responses are speculation.
However, if I may speculate:
I've seen this once or twice with heavily edited code. WinXL/VBA is better at dealing with code corruption than MacXL/VBA is. So it might be worth it to try cleaning up the internal code modules.
If you have access to 32-bit WinXL, run Rob Bovey's Code Cleaner.
Otherwise, if you can open the file on either platform:
In the Visual Basic Editor:
- For each regular or custom class code module, copy the text and paste as plain text to a text editor (using one or more text files)
- If the code is in a regular code or custom class module, note the name of the module in your text file, then delete the module
- If the code is in a built-in class module (e.g., ThisWorkbook, Sheet1. etc.), select all of the code and delete it
- Save the XL file as a new file and close XL (the latter is probably not necessary, but it won't hurt).
- Open the new file (after renaming, if desired)
- Copy the code from built-in class modules in the text editor to the new workbook's built-in class modules.
- Recreate each regular or custom class module, rename it appropriately, and copy the corresponding code from the text editor file to the new module.
- Save the XL file.