Shown here is an example of the contents of the
ApplicationText.ini and
ApplicationTextBase.ini files,
followed by a description of this format.
[Customers]
module=Customers
object.MainObject=Main Object
property.MainObject.Customers=Customers
object.Customer=Customer
property.Customer.CustomerID=ID
property.Customer.CompanyName=Company
property.Customer.ContactName=Contact
Note: The contents of this file are application-specific and
will differ from one application to the next. The above is an example
for a mobile application built for the Northwind demonstration database
in SQL Server.
This override file contains one section for each module defined
within the application, named [ModuleName],
and one section named [Misc.] for the application-level
definitions. Any items listed under a section name are part of that
section.
The second line in the above example,
module=Customers,
represents the display name of the module. Each override item’s
key follows a defined format:
defType.ModuleLevelParent.parent.parent.definitionName
The following items are the explanations to each component of
the key:
- defType: The type of definition
that is overridden by the item. Examples include:
- property
- object
- platform
- listscreencaption
- ModuleLevelParent: The name of the module-level
parent definition of the definition whose display value is overridden.
- Parent.Parent...: The name of each ancestor
definition between the module level ancestor and the definition
that is overridden.
- definitionName: The name of the definition
that is overridden.
The last line in the above example, property.Customer.ContactName,
contains the override value for the display name of the property in
the Customer object named ContactName.
All definitions within the application with a display name, label,
or caption attribute are listed in this file.