I frequently handle Excel files with VBA macros written in Japan. Multiple times over the last few years, I have had macros that previously worked stop working on the same machines they've been working on. The computers haven't been changed as far as I know (of course corporate IT are constantly changing group policy and endpoint AV software!)
The problem is always the same: the macros are using variable or subroutine names written in Japanese, and they show up with garbled encoding. In the past, I've asked for support from the macros' various authors, and I think they fixed it by just changing the problematic areas into Latin characters. This time, I looked into it more and found this previous post, and changing the non-Unicode language settings like this fixed the issue: Region settings in Windows showing non-unicode language set to Japanese
My question is this: why did these macros work before I changed this setting to Japanese? I know it was set to English before, because it was always using code page 437 in Command Prompt. Is there any way that a macro written with Japanese characters can execute correctly on a machine set to English, then stop working? I'm trying to figure out more about how this all works so that I can better support future issues.
Thanks in advance to anyone who takes the time to respond!
