-
[quote user="waleed Awny"] and for the crylic language, its Mongolian Crylic, so after translating NAV (which was not easy cause its is not provided by microsoft) we imported the language file and we just create a floder under the Program file called MON, and then you'll have 2 options...
-
[quote user="waleed Awny"] and for the crylic language, its Mongolian Crylic, so after translating NAV (which was not easy cause its is not provided by microsoft) we imported the language file and we just create a floder under the Program file called MON, and then you'll have 2 options...
-
I have been asking around the last 5 years to different MS employees to find an optimal collation. What we want is: a single database / datastore for all countries (and of course validate codepage is deactivated) a collation that supports the sorting of most languages (however recommend e.g. turkish...
-
Hi Dean, I don't understand why you say that will not work. I have had one database the last 5 years including of course western european and US languages but also include Korean, Chinese and Turkish. It works fine with the SQL collation as described but if using windows collation it gives the noted...
-
Ok, I know we have two collation threads running right now. So I would like this thread to continue and the other to stop. [quote user="Dean McCrae"] If I was using a database with Chinese/Japense/Korean characters, which are double-byte (when not Unicode), then its quite another situation...
-
[quote user="Dean McCrae"] Since NAV does not utilize either collation types as Unicode, you need to ensure that code pages are fixed, or use characters that do not suffer under conversion. [/quote] Ok, how would you then setup the server/database to allow have both ex. Danish, Greek, Turkish...
-
[quote user="Dean McCrae"] In general, Windows collations are a better choice because they use the operating system's API for comparisons (or a snapshot of it at least) which in turn, many common desktop applications also use - so it is more standard. Added to this, SQL collations are likely...
-
The collation setting that you choose from Navision is a database-wide setting that will affect all character data types in the database - meaning Text and Code fields from Navision's view. Navision does not make use of column-level collations, although this is the granularity provided by SQL Server...
-
Thanks for the answers, but there seems to be a little disconcern about the sql-type varchar collation-dependence. In MSDN one can read: "Objects that use char or varchar are assigned the default collation of the database, ...", which I interpret in such a way that Navision Code fields (varchar...
-
The Windows collation for: "Afrikaans, Basque, Catalan, Dutch, English, Faeroese, German, Indonesian, Italian, Portuguese" should give you close behaviour with your native database, checking also the Case and Accent senesitive boxes. The biggest difference will be for Code fields that, by default...