Upgrade Toolkit

Chapter 3. Upgrading to Multilanguage
22
You must now repeat the process of translation for the old base version if your local
Microsoft Business Solutions office has not made this database available to you in
English.
The result of this process is that the old base version, the customer’s current database
and the new Navision database will all have the same code base language and you
can compare them in order to transfer customizations from the old database to the
new.
The translated name properties and variables will make it easier for you to compare
and merge the old and the new databases. For more information about merging, see
Chapter 4, Merging on page 37.
Transferring Object and Field Names
If you do not have access to the translation database, or if the customer’s database
has not been heavily modified, you can merely import the Navision object and field
names into the old base version and into the customized version. As a result, the
merge will be easier as you will not have to manually merge the object and field
names.
References to base version field option values, variables and user defined functions
are not handled by this process, however, so they must be handled manually during
the merge. You can import object and field names from the new base version without
risking errors, because once an object or field is assigned a number, guidelines
ensure that it is never assigned to other objects or fields.
Creating New Base Translation File
In order to proceed with the translation and conversion, you need a translation file with
all text strings from the new Navision database. You use this file first to create a file
with names of objects and fields and then to be used as a memory file in connection
with the conv-ml tool.
To create the new base translation file:
1 Open the new base version, Navision.
2 Click Tools, Language and select what language to work with.
As described on page 16, you must be consistent in the use of current language.
3 In the Object Designer, select all objects and click Tools, Translate, Export.
4 Save the file as w1360client.txt, where w1 is the country code, 360 is the
version of the application, and client.txt indicates the file type.
Creating Object and Field Names File
You must now use the new base translation file to extract names of objects and fields.
The target file will then be used to change the language of object and field names in
base version objects.