That's exactly the approach I use in my applications.
All string ressources are compiled in a language specific dll.
When the user logs in he/she can choice the language which should be
used. The language dll is loaded at runtime and all dialogs load
their strings dynamically.

Of course, this needs some additional programming work but I think
this is the most flexible way. All string ressources are contained in
a ressource file (.rc). If a new language is needed, only this file
needs to be translated to compile a new language dll. No need to
recompile the application.

I have written a few components which deal with the DLL handling to
make the developer's live easier. If anyone is interested in these
components, email me privately.

Mario

--- In IBObjects@y..., "Jason Wharton" <jwharton@i...> wrote:
> I thought that using the resourcestring instead of const would allow
> flexibility to do it both ways. No?
>