NAV vs DBCS


We recently faced a challange to setup bussiness in Japan. We all know that NAV is NOT Unicode and therefore it does not support the Japanese characterset which is a DBCS.

How do we proceed in this case? What are the steps needed to get the NAV database up and running?
These were just some of the questions I had. There wasn’t much information I could find on the net regarding this issue. Having some support calls logged with MS helped solve alot of issues.

Anyway, in this post I will share with you all how we were able to make this installation successfull.

What is DBCS?

DBCS stands for Double Byte Character Set. In CJK (Chinese, Japanese and Korean) computing, the term “DBCS” traditionally means a character set in which every graphic character not representable by an accompanying SBCS is encoded in two bytes; Han characters would generally comprise most of these two-byte characters.

The NAV STX file:

The first thing you need is a new stx file which has been sealed with the “Allow DBCS” switch on.

// 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 database code page is a non-DBCS code page   
00093-00400-010-2: 1 

Sealing this stx file can only be done by microsoft. Send them your STX file and you will receive a new one with DBCS enabled.

The Japanese Language pack:

The next step will be to install the Japanese language pack. There is NO official language pack from Microsoft available. You will need to contact a local solution center in Japan to obtain it. This language Pack will have all the menu items, forms and tables translated.

Now you can try and open NAV. If the database server is running on a English OS using the 1252 latin codepage, you will NOT see any japanese characters. The only thing you will see are meaningless ASCII sings. To be able to see the Japanese text, you will need to set the regional settings for the server.

Regional Settings:

Go into the control panel > Regional and Language Options.
In here you need to Install Files for East Asian Languages in the Languages tab. (This will enable the OS to display Japanese text in menus)
Next up is setting the language used in Non-Unicode applications, such as Navision.
Set this selection to the Language needed for the NAV database. In my case this was Japanese.

Finished!

After this you will be able to display the Japanese characters in NAV.
The data which is in SQL however, is still displayed in this ASCII sequences. It is Windows who actually converts these ASCII characters into the correct Japanese character because of this Non-Unicode app setting.

Advertisements
Tagged with: ,
Posted in NAV
6 comments on “NAV vs DBCS
  1. Tugy says:

    Hi, im looking for a Japanese Language pack, but i just cant find one online.
    Could you send your Language pack to me?

  2. Kenny Vaes says:

    Hi Tugy,

    The Japanese language pack isn’t an official language pack provided by MS. You will have to enquire it by contacting a local NAV partner in Japan. They will also have the Japanese localizations.

    Pacific Business Consulting, Inc.
    http://www.pbc.co.jp/en/

  3. Sam says:

    hi,

    i am trying to import Japanese (Kanji) characters in navision database through data port.

    After changing the System Locale to Japanese, i able to see some Japanese chars in navison database but its different which i imported from text file. ( i mean imported .txt file and navision data are totally different).

    Also the same if am exporting from navision using same dataport , its showing correct data in .txt file which i tried to import earlier.
    ex:
    imported char like タ
    Navision Data : 法人
    Exported data : タ

    used Database : Nav 2009 SP1 w1, SQL Server 2008 R2

  4. Sam says:

    hi,

    missed to add, if am copy paste from .txt file to Navision database its working fine.

    through dataport its creating issue

  5. It’s the best time to make some plans for the future and it is time to be happy. I’ve
    read this post and if I could I wish to suggest you some interesting things or advice.
    Maybe you could write next articles referring to this article.
    I want to read more things about it!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: