I would suggest doing this as a two step process with a specific, and relatively simple, data structure: a table with columns: Control ID, Language ID, Text, Left, Width, Top, Height.

Adding a new language would be something done at design time. The first step is to add the text for the language.

I haven’t done much programming in the VBE environment. So, I don’t know how easy the following is. At worst, one can always do what’s needed “by hand.” {grin}

Now, (use code to?) update the userform (or whatever UI you are using) with the new text. With the new text in place, adjust the userform controls so that they are readable and aesthetically appealing.

Now, update the table with the controls’ dimensions.

The runtime MLS support code works with both the language text and control position/size.

The task of handling error messages should be a lot simpler…I think…

Separate sheet with the first column being the unique identifier, and then a column per language. Display text is generated by finding the unique id (say lanMailSignoff or lantbCustomerName) and then using the language offset to find the text.

I think I’d be inclined to create some sort of enhanced Dictionary (there’s a clue in the class name) that loads itself from some text resource, which could be a hidden worksheet, a module (ugh) or something external – text file, MDB, XML, whatever. Call it a Translator, perhaps.

Beyond that, I think I’d consider using some sort of magic to indicate the controls that needed to be considered: maybe use the Tag property, if it’s free? Maybe put a “C” for caption needed, an “A” for accelerator and “AC” for both.

Now my workflow can be something like this:
1. Determine language and load my Translator
2. Pass the form to the Translator, which works through the controls, setting properties as needed.

I kinda hope that would work. I might even build a Collection or Translators (is there a collective noun? A Tower? As in Babel?) so that I could switch on demand, perhaps within a loaded form. It shouldn’t take more than a few lines of code.

This is less work than it sounds: after you’ve written and tested the application, a short VBA subroutine can enumerate all the controls on each form and spreadsheet, and write a tag of ParentName;ControlName;EnglishCaption into each control’s tag property AND to a hidden sheet, with the parent object name in column A, the control name on’B', and the English caption in ‘C’ under the column heading ‘English’.

Now fill in the next column under the heading ‘French’, the next one in ‘German’, and so on. Advanced students may want to specify a code page, although this can be picked up from the registry too.

On open, a subroutine queries the locale in the registry, then fills in all the captions. It is possible to fill in entries manually for chart captions and labels, a more difficult item to enumerate in code.

It can be done without tags at all, but self-documenting controls are easier to debug!

Apologies for not supplying the source code but I’m away from my PC.

I have seen them other programes that do this, I think it makes sense.

On application load or language change I read the file and store the strings in a scripting dictionary. On form load I fill the needed captions, tooltips and messages from the dictionary. I prefer to use a function for all calls to the dictionary so I can trap missing ID’s. ..

You’ll find that most languages require more space than English. Hungarian is even worse than German (or maybe it’s my translator who needs more words?) Just keep plenty of space. I never use autosize and textwrap for my controls.

See:

http://www.jkp-ads.com/articles/distributemacro09.asp

The code for reading the strings is a bit clumsy, but it works fine.