Which Collation to use for South Korea in SQL2008?

BVS

Hi,

We are using :
Microsoft Dynamics 2009 R2 Version W1 6.0 R2 SPIW12.01.00 QM4 (6.00.32012)
World Wide version ENGLISH.
Classic Client (CC)

Navision Database : Collation Tab.
Collation Type : Windows Enabled.
Validate Collation : Disabled
Collation Description : Afrikaans, Basque, Catalan, Dutch, English, Faeroese, German, Indonesian, Italian, Portuguese
Binary : Disabled
Case-Sensitive : Enabled
Accent-sensitive : Enabled

Workstation to test company Korea: Windows Server 2008 English
Control Panel > Regional and Language Options > Administrative tab
Change the current language for non-Unicode programs to: Korean (Korea)
Keyboard settings : Korean (Korea)

Problem:
In Navision when entering some Korean letters appears a ?
1. "ㄹ" : It sounds like " R or L" and it is located on "F" key.
2. "ㅁ" : It sounds like " M " and it is located on "A" key.
3. "ㅈ" : It sounds like " J " and it is located on " W " key.

Tried the following collation with all same wrong results.
Latin1_General_CS_AS_WS
Korean_Wansung_CS_AS_WS
Korean_100_CS_AS_WS
Korean_190_CS_AS_WS (Not supported)

Any comments would be appreciated.

Thanks
Bob

Ploeg

Microsoft's MSDN says Korean_Wansung_CI_AS... but I wouldn't know if it works. :?:

Emil-Korea

Hello,

I'm working at BSE Consulting Korea. I may be able to help you with your questions.

The SQL database for NAV should always be latin.
It will be broken in the database but appear correctly in NAV.

If you need a Korean SQL database for something else, Ploeg is right.
You should use this collation: "Korean_Wansung_CI_AS"

Regards,

Kevin_R

I have Navision 5.0 running this way. On Latin Collation, with Korean characters stored in the description field. If I wanted to run reports off of the SQL backend, is there and easy way to get these Korean characters to show up?

Emil-Korea

Hi,

Well one solution is to create a clone table that will use "Korean_Wansung_CI_AS" collation.

Best Regards,