maratoolFix #NAME? errors: Excel formulas across languages
You copied =VLOOKUP(...) from a tutorial, pasted it into Excel in Portuguese, and got #NAME?. The function exists; its name doesn't.
Excel translates function names with the interface language. =SUM() becomes =SOMA() in Portuguese and =SUMA() in Spanish; VLOOKUP becomes PROCV and BUSCARV. Paste an English formula into a localized installation and Excel doesn't recognize the name, so it returns #NAME? and you're left guessing. The Excel Formula Translator is the guessing removed: all 375 function names in the three languages, searchable from any of them, click to copy.
How it works
- Type a function name in English, Portuguese, or Spanish (accents optional).
- The table filters to matches and shows the row across all three languages.
- Click the name you need and paste it into your formula bar.
The names are only half the fix
Two more things change between localized versions. Logical constants translate: TRUE/FALSE are VERDADEIRO/FALSO in Portuguese and VERDADERO/FALSO in Spanish. And the argument separator often switches from comma to semicolon depending on regional settings, so =VLOOKUP(A2, table, 2, FALSE) becomes =PROCV(A2; tabela; 2; FALSO). If a translated formula still errors, check the separators.
When you don't need to translate anything
Files store formulas in a language-neutral internal format. Open an .xlsx made in English on a Portuguese Excel and every formula displays already translated. Manual translation only matters for formula text that travels as text: tutorials, Stack Overflow answers, documentation, code that writes formulas into cells. Newer functions like LET and LAMBDA keep their English names everywhere, so there's nothing to translate there.