Localization Tables

The following Database Diagram shows two tables that are used by MM .NET for localization purposes:

Here is a description and structure of each table:

Note: You can add new fields to the localization tables without affecting MM .NET. However, if you change the name of a field, you must also make a change to the corresponding security business object. For details, see the Help topic Localization Business Objects

Language

Contains all languages for which the application has been localized. The culture field contains one of the culture names listed in the .NET Help topic "CultureInfo Class"

Message

Contains all framework-level messages. The LanguageFK field specifies the foreign key of the language with which the message record is associated. A LanguageFK value of one (1) indicates the developer's original language. The message table can contain multiple records with the same MessageKey value, but with different LanguageFK values. The DialogText field specifies if the text is displayed in a MessageBox-style dialog that is not accessible from the MM .NET localization builders at run time. All records that have this value set to one (1) is displayed in the Localization Form when translating messages.

Referential Integrity

The MMLocalize.sql script adds referential integrity for cascading deletes in the localization tables. Here are the constraints that are automatically added for you:

Language.LanguagePK
  --> Messages.LanguageFK

So, if you delete a language from the Language table, any records for that language in the Messages table are automatically deleted.

Setting up the Localization Database

For information on setting up the localization database, see the Help topics Adding Localization Tables to a Database,Moving .