Thank you for this advice. I already handle translations for strings and messages in tables. I have a function to get the translated strings and messages. But the messages here are to be used at the very beginning of my app. This is for the situation, that a new build is installed and table structures are to be changed. In this case I do not want to instantiate any classes so that I do not block myself by any chance.

Thank you again.
Gerhard

>One piece of advice - don't program it. Put those in a table ( you can include the table in the project if needed)
>
>>I think of something like this
>>
>>DO CASE
>> CASE cLanguage = "D"
>> cMsgText = "Beschreibung des Fehlers."
>> cMsgHeader = "Fehler"
>> CASE cLanguage = "E"
>> cMsgText = "Description of Error."
>> cMsgHeader = "Error"
>>ENDCASE
>>
>>MESSAGEBOX(cMsgText, 0, cMsgHeader)
>
>
>
>>
>>>>>>This is to give messages in a language depending on the user's language.
>>>
>>>What code does that?
>>>
>>>>I don't understand your "What do you use". Can you please explain?