This page (revision-4) was last changed on 26-Nov-2021 10:22 by rforbes

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
4 26-Nov-2021 10:22 5 KB rforbes to previous
3 26-Nov-2021 10:22 5 KB JEscott to previous | to last
2 26-Nov-2021 10:22 5 KB JAiken to previous | to last
1 26-Nov-2021 10:22 5 KB JEscott to last

Page References

Incoming links Outgoing links
TRANSLATION LEXICONS TO CTL FILE
TRANSLATION LEXICONS TO CTL FILE

Version management

Difference between version and

At line 86 changed one line
As you can see from this example, the translation is actually performed by a stored procedure created by High Line call P2K_SMGLX. This function takes two parameters and returns a string for the translation. The first parameter is the lexicon name that was created to hold the translation list, the second is the field that contains the coded value that needs to be translated. In this example the field that contains the coded value is the same field that the translation is being performs on, but this is not a requirement. It is possible to use any column, or set of columns, in the records for translation.
As you can see from this example, the translation is actually performed by a stored procedure called P2K_SMGLX. This function takes two parameters and returns a string for the translation. The first parameter is the lexicon name that was created to hold the translation list, the second is the field that contains the coded value that needs to be translated. In this example the field that contains the coded value is the same field that the translation is being performs on, but this is not a requirement. It is possible to use any column, or set of columns, in the records for translation.
This page (revision-4) was last changed on 26-Nov-2021 10:22 by rforbesTop