SQL Option for Navision 3.6 problem

To All, Server Setup : Windows 2000 Server SP3 (English) - Set default locale : English (US) MS SQL Server Standard Edition (English) - Set as SQL Collation 1252 Client Side : Navision 3.6 SG Build 11353 Creation/Access of New/Created Database (This means during creation of new database or access of existing database) From Windows 2000/XP SP1 (English) : NO PROBLEM From Windows 2000/XP SP1 (Japanese) : ERROR “The double byte character set code page 932 on your computer is not supported by the current version of Microsoft Navision Attain” Does This mean that Navision 3.6 is not yet compatible to Japanese OS clients? Any ideas? Regards, Marlon

I think the codepage needs to be the same on all clients and the server, since Nav doesn’t support different codepages.

It means that your client computer (and all other clients using Japanese) is using the 932 code page, which makes sense. This code page is a Double-byte character set (DBCS) code page. Both Attain and SQL Server have limitations with this type of code page, which effects sorting, comparisons and lengths of data in the database. There is a flag in the .stx file which allows the use of a DBCS code page on the client. This is the relevant section: ================================================================ // The following entry is for double-byte character set (DBCS) clients (code pages 932, 936, 949, 950) // A value of 0 indicates that a client DBCS is disallowed // A value of 1 indicates that a client DBCS is allowed, provided that the server code page is a non-DBCS code page 00093-00400-010-2: 0 ================================================================ So change the last 0 to a 1 to allow a DBCS client code page. This must be done by someone with the ability to seal an stx file. You can then use a SQL Server database but you must ensure that the database collation is NOT a DBCS code page; i.e. NOT a Japanese collation. You must choose a single-byte character set (SBCS) collation such as Western European collation. You can choose either a dictionary sort order or binary sort order for your chosen collation; binary is probably better since it will group the DBCS characters more sensibly than a dictionaty order (contrary to the normal situation with SBCS). I know that this has all been tested with a 1252 code page binary collation, with Japanese client machines, and the sorting was acceptable. One more thing. Since DBCS stores characters of either 1 or 2 bytes depending on the data, it is not known how long a text string will be and you may exceed the max size for some of your Code or Text fields in your tables. You may need to extend them.