> I need to covert an existing system to Support Multiple Languages, at 
least
> 4 for now. Any one have some words of advice or suggestion on design.

Resource files are the obvious ones. You can also write your own 
translation modules which can then be dynamically updated by translation 
punters rather than having to be compiled by programmers - we've done a 
system like this recently, and it was much simpler than VB resource files.

However, there can be other gotchas :-)

For example, be very careful with your date and numeric types, and how you 
display them and save them. Different date separators and decimal 
delimeters can trip you up at the best of times. I've spent a while 
debugging some code writing to a JET database, using direct SQL rather 
than ADO/DAO, using the #mm/dd/yy# syntax. This gets screwed using Finnish 
as a language - they also use a comma as a decimal separator, so if you 
save numerics to an INI file in one language, and try and read them back 
in another, you will get type mismatches. And again, JET will barf if you 
point a double at it with anything other than a US style . as the decimal 
delimiter.

Good luck !

Paul Bradbury,
Birmingham, UK