-
If you want to have one database for all countries for SQL2000 (one collation for all asia countries) the best collation according to ESG (now Tectura) is: "You must use SQL Collation if you are using double-byte. For optimal performance, you should choose Western-European dictionary sort order...
Posted to
Dynamics NAV / Navision - Technical Forum
(Forum)
by
Kim Mohr Larsen
on
Aug 18, 2006
Filed under: Asia, Hong Kong, Australia, China, Japan, Singapore, Code Page, Dynamics NAV, Collation, APAC, Double Byte Character
-
Well we have a so-called APAC (asia pacific) database which should cover all our APAC companies. These run in countries such as Japan, China, Hong Kong, Singapore and Australia. Today only our Japanese company runs it it. And this is due to the fact that the collation is set to Japanese. Which collation...
Posted to
Dynamics NAV / Navision - Technical Forum
(Forum)
by
Erik P. Ernst
on
Jun 13, 2006
Filed under: Asia, Hong Kong, Australia, China, Japan, Singapore, Code Page, Dynamics NAV, Collation, APAC, Double Byte Character
-
Most users work only in English, but some Chinese and especially Japanese is also used especially in name, address and description fields.
Posted to
Dynamics NAV / Navision - Technical Forum
(Forum)
by
Erik P. Ernst
on
Jun 14, 2006
Filed under: Asia, Hong Kong, Australia, China, Japan, Singapore, Code Page, Dynamics NAV, Collation, APAC, Double Byte Character
-
Can it really be true that nobody knows anything about this??
Posted to
Dynamics NAV / Navision - Technical Forum
(Forum)
by
Erik P. Ernst
on
Jun 22, 2006
Filed under: Asia, Hong Kong, Australia, China, Japan, Singapore, Code Page, Dynamics NAV, Collation, APAC, Double Byte Character
-
Good question. Do all users work in English or do they work with local languages in script?
Posted to
Dynamics NAV / Navision - Technical Forum
(Forum)
by
jsrark
on
Jun 14, 2006
Filed under: Asia, Hong Kong, Australia, China, Japan, Singapore, Code Page, Dynamics NAV, Collation, APAC, Double Byte Character