Originally Posted by
Ajax
The way I handle languages is to have an admin table along the lines of
PK
Phrase
LanguageFK
Translation
Then I have a function in a standard module that accepts the form object and languageFK as optional parameters
the function
1. only runs if the language is not the development language
2. creates a static recordset of the records for the specified language if not already created so this normally run when the db is first opened or user logs in
3. then loops through the form for captions and finds matches in the recordset for the caption and updates the form and control captions accordingly
There are other translation functions to handle things like messages (gets complicated when the message is dynamic!) and a developer option to identify captions without a translation
So I use a standard module rather than a class module.