German language issues with macros - Office 2003 version

[Colinhp]

I work in a company with users in Germany, France and Spain. Their computers
would be set up for their native languages.
They can not open or use a tool I created in Excel which has macros written
in English. My computer is set up for UK use.
Is there additional code I should be writing for these users, that converts
English to their native language or are macros universal in their behaviour?
If the answer is yes, what is it I should be adding?
Many thanks.

 

[raypayette]

Personally I think that everyone should use the English version. Here is
a link that misht help, but the conversion would be a chore, even with
an appropriate "replace" procedure.
http://cherbe.free.fr/traduc_fonctions_xl97.html

 

[Kevin McCartney]

Hi Colin,

I've written several macros/vba code in English and my workbooks have been
used all over the Globe. There was no additional code required. Your problem
may lie in how you're referencing items within the Excel environment, e.g.
menu items by name a spelt differently but their menu IDs are the same, so
reference menu items by ID and you'll be OK. Formulas are also different but
if you're updating cells with formulas by code then you should be OK in that
Excel will translate them for you.

Can you be a little bit more specific about what error message(s) your end
users see when they try to start your Excel workbook add-in. It would help to
narrow the problem down a lot more if you had specific line statement.

Hope to hear from you
ciao
KM

 

[keepITcool]

VBA works in all languages.(there is no "German" VBA.)

You must however ALWAYS keep regional settings in mind when you
write software. (. or , for decimal etc etc)

Your code can easily be tested on your english setup,
by simply changing Regional Settings.
(string to number conversions will be your main problem here
when you take numeric user input from text boxes .)

When your code adds formulas to a sheet, or manipulates Names
avoid FormulaLocal, always use Formula.
avoid RC, use A1 notations.
(and english function names, . for decimal and , for list separator)

When your code adds Dates use variables defined as Date.
(then READ/WRITE them to .Value2 property of cells.
Cell.Value2=cdbl(mydate)


Without seeing your code there is no general recipe...
Start with changing your regional settings to German.
adapt your code to take care of date and decimal stuff.

Then ask a foreign colleague to test. If some things still dont work,
isolate the problems and post back here with specific questions.

HTH


--
keepITcool
| www.XLsupport.com | keepITcool chello nl | amsterdam


Colinhp wrote in

 

[NickHK]

From what I understand, Excel will translate function names used on
worksheets if opened in a different language, as what you see in the cell is
only an alias for the internal name.
However, VBA code is not included in this process.
may be this will help:
http://www.rondebruin.nl/atptranslator.htm

NickHK

 

[Dave Peterson]

You may want to look at John Green, Stephen Bullen, Rob Bovey and Robert
Rosenberg's book:

Excel 2002 VBA Programmer's Reference
http://www.oaltd.co.uk/ExcelProgRef/Default.htm

They have shared a chapter on international issues.
(direct link: http://www.oaltd.co.uk/ExcelProgRef/Default.htm)

 

[Colinhp]

Hello everyone,

Many thanks for all your comments. I will follow up the users and find out
what the exact issue is before trying out some of these solutions.

Many thanks for all your help.

Colin.

 

[bplumhoff]

Hello,

1. Easiest solution would be a company-wide standard (English MS-Excel,
you can find this in many investment banks/financial companies).

2. Most frequent problems between English and German:

a) Date-Formats ("MM/DD/YYYY" or "DD/MM/YYYY" vs. "TT/MM/JJJJ")

b) ...formula.local in VBA (do NOT use this!)

c) Analysis-Addin: Functions are named differently in English, German,
French, Spain...

I suggest to try 1. first. If you need your application(s) to be
adapted to all individual country-specific versions: Get all these
versions, seek/develop the smallest common multiple and test it
thoroughly...

Regards,
Bernd