Hi John,
I responded to your post under Reports & Report designer. I do similar language conversion in reports and on all forms, not so much for internationalization but for different nomenclature. The language table consists of a string ID, defaulttext, and currenttext fields. Column headings and localized captions are assigned to variables before report is run and the variables are referenced in the report form. This prevents re-run of your localize UDF each time the report moves to a new page (or if using localized text in detail band, for each record).

On forms, each object that is to be localized has a "defaultcaption" property. In the init of each control, the defaultcaption property is set to the designtime caption, the defaultcaption is looked up by the localize function and object.caption is replaced with the localized string. I also allow the user set the application in translate mode and change captions (by right click on each caption) to change the current language caption if the want to change language or nomenclature. A different language table can also be created for each supported language, translated by a hired translator if you wanted to create multiple language files.

Although my functions were not primarily designed for internationalization, it should lend itself to that purpose, however, there may be some codepage issues that I have not encountered.

HTH
Elmer