Creating Missing Message Translations Records

If you use your application’s Message Manager to create a message, Visual ProMatrix will automatically create Message Translations records for each language in the application when you save the message. All you will then need to do is enter your message translations using the Message Translations form.

However, when you are ready to enter message translations, you may have “missing” Message Translations records if any of the following occurred:

·       You created a message using the Message Builder in VPME instead of the Message Manager in your application.

·       You added a language to your application after you created some or all of your messages.

Now, you can always manually create the Message Translations records that you need using the Message Translations form. You can click the New toolbar button and enter the Message ID, Language ID and message translation. However, that’s laborious and tiresome. Fortunately for you, there is a way to let VPME automatically create “missing” Message Translations records for you:

·       Language Manager – Create Message Translations: You can run the Create Message Translations utility from the Language Manager to let VPME automatically create the “missing” Message Translations records for you.

Language Manager – Create Message Translations

After you have created all or most of your application’s messages, use the Language Manager to create missing Message Translations records. You can reach the Language Manager from your application’s Admin menu.

Ř To create Message Translations records with the Language Manager

1.   Run the Language Manager and display the language for which you want to create Message Translations records.

2.   Click the Create Message Translations button at the bottom of the form. The Language Manager will automatically create missing Message Translations records for the language displayed. One record is created in the Message Translations table for each message in the Messages table with the Message ID and Language ID fields filled in.

Tip: Of course, a Message Translation record will not be created in the Message Translations table if it’s already there. In other words, if a record already exists in the Message Translations table with the same Message ID and Language ID as a record about to be added to the table, the record will not be added.

3.   Repeat for Each Language: Normally, you would want to create Message Translations records for each language in an application. Therefore, repeat steps 1 and 2 for each language in your application. You will then have a set of Message Translations records for each language.

More:

Entering Message Translations