Hi,
It does work at run time as well, but with a little differenet approach. What we did earlier for run time language selection is as
follows.

In the main form there is a menu - Language and submenus as English Spanish etc
The Res file is compiled as a VB activeX dll along with a class name like CReadLanguageRes.cls
this class just has one public method which calls LoadResString from the RES file added to that.

This is done for all languages used. So there will be English.dll,  Spanish.dll etc each has the same class file but a diff res
file. Since U have already have some working solution, I think u got the message. U can do similar thing, the idea is separate the
languagae related stuff outside the main application code.

T.Mahata



From: "Grant Pelach" <Grant.pelach@a...>
Date: Thu, 23 Aug 2001 20:15:10
X-Message-Number: 11

We built an application to produce a a resource file for multiple 
languages. We can run a converted application in design time and it will 
choose the proper language resource based on the regional settings in 
windows. However in runtime application uses the registry setting, which 
is hex 409 for English. When we manually change that registry entry on a 
test machine we could run in the language we wanted to. The question is 
why does it work in design time and not runtime? And are there any 
workarounds tricks, command line parameters, compiling options, etc. That 
would allow us to change languages on the fly without rebooting while 
still being able to use the resource file ? 

----------------------------------------------------------------------