dbTalk Databases Forums  

ADOMD problem with Korean regional setting on Windows

comp.databases.olap comp.databases.olap


Discuss ADOMD problem with Korean regional setting on Windows in the comp.databases.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Jothi
 
Posts: n/a

Default ADOMD problem with Korean regional setting on Windows - 08-25-2004 , 10:20 PM






In our application we use Microsoft ADO-MD to access Korean and
English cubes. When we tried to localize the application to Korean, we
found ADOMD does not execute rank command with Extract part having
dimension name in korean language. Even when I run the "MDX Sample
Application" which comes with Analysis Services 2000, the query throws
error saying "Token is not valid". But the same query having dimension
name in English connecting to English cube works fine..

I am using Windows 2000 Professional with "Korean" set as the default
regional setting. "Microsoft ActiveX Data Objects (Multi-dimensional)
2.5" is present on my machine and the application is written in Visual
Basic 6.


Query fails - I have marked the query part in BOLD and RED colour font
which is shown as a error in MDX Sample Application.:
Rank creation(Connecting to Korean Cube):
CREATE SET [DBCS_KOR_CHAR_9998082__20040430].[#SERVER#G
SET2#ア箍」#REL#SSG1000000001#IMS1#&@SSG1] AS
'{[#SERVER#G CALC#ア箍」#REL#SSG1000000001#&@SSG1]}'
SET [DBCS_KOR_CHAR_9998082__20040430].[#SERVER#G
SET2#ア箍」#REL#SSG0000000002#IMS1#&@ssg] AS
'{[#SERVER#G CALC#ア箍」#REL#SSG0000000002#&@ssg]}'
SET [DBCS_KOR_CHAR_9998082__20040430].[IMS1チョヌミ]
AS '{{[チョヌミ].[GEO].[All
Geography].[423A#&@ネ」チヨ]}}' SET
[DBCS_KOR_CHAR_9998082__20040430].[IMS1チヲヌー]
AS '{{[チヲヌー].[MKT].[All
Product].[0#&@ヌユー·ステタ蘊}}'
SET [DBCS_KOR_CHAR_9998082__20040430].[IMS1ア箍」]
AS '{{[ア箍」].[REL].[0#&@クホ_ー·襍ヌエツ_ステー」].[M013#&@タフオソヌマエツ
ソャキハ
ヌユー·4エ゙
2003].[S019#&@ヌミア·10エ゙
2002].[Q022#&@ウサケォケン
7エ゙ 2002].[P024#&@エ゙ 5エ゙
2002]}}' MEMBER [DBCS_KOR_CHAR_9998082__20040430].[Measures].[#RANK#IMS1#チョヌミ#&@rank]
AS
'RANK(([チョヌミ].[GEO].CURRENTMEMBER),ORDER({{EXTRACT({IMS1チョヌミ},
[チョヌミ].[GEO])}},([Measures].[ー。ト。
ー「タレ エレナヘ]),
BDESC))', SOLVE_ORDER = 1000, FORMAT_STRING = '#' SET
[DBCS_KOR_CHAR_9998082__20040430].[IMS1MEASURES] AS '{{[Measures].[
ー。ト。]}}' SET
[DBCS_KOR_CHAR_9998082__20040430].IMS1SLICE1 AS
'{[IMS1チヲヌー]}' SET
[DBCS_KOR_CHAR_9998082__20040430].IMS1SLICE2 AS
'{[IMS1ア箍」]}'

Query executes successfully:
Rank creation(Connecting to English Cube):
CREATE SET [USERDEMO 1 4 U ABC C99980_4325__20030218].[IMS4GEOGRAPHY]
AS '{{[GEOGRAPHY].[GEO].[All GEOGRAPHY.GEO].[C00000000#&@NATIONAL]}}'
SET [USERDEMO 1 4 U ABC C99980_4325__20030218].[IMS4PERIOD] AS
'{{[PERIOD].[CAL].[MALL#&@ALL_CALENDAR_PERIOD].[CYR02#&@CALENDAR_YEAR2002].[CS0202#&@CALENDAR_SEM02/2002].[CQ0203#&@CALENDAR_QTR03/2002].[M02070207#&@MNTH-07/2002]}}'
SET [USERDEMO 1 4 U ABC C99980_4325__20030218].[IMS4PRODUCT] AS
'{{[PRODUCT].[MKT].[All PRODUCT.MKT].[G00000000#&@TOTAL MARKET]}}'
MEMBER [USERDEMO 1 4 U ABC
C99980_4325__20030218].[Measures].[#RANK#IMS4#GEOGRAPHY#&@rank] AS
'RANK(([GEOGRAPHY].[GEO].CURRENTMEMBER),
ORDER({{EXTRACT({IMS4GEOGRAPHY},
[GEOGRAPHY].[GEO])}},([Measures].[SALES PER PHARMACY]), BDESC))',
SOLVE_ORDER = 1000, FORMAT_STRING = '#' SET [USERDEMO 1 4 U ABC
C99980_4325__20030218].[IMS4MEASURES] AS '{{[Measures].[VALUES]}}' SET
[USERDEMO 1 4 U ABC C99980_4325__20030218].IMS4SLICE1 AS
'{[IMS4PERIOD]}' SET [USERDEMO 1 4 U ABC
C99980_4325__20030218].IMS4SLICE2 AS '{[IMS4PRODUCT]}'

Below query executes fine. This query also uses rank but not having
Extract part.
Rank creation(Connecting to Korean Cube):
CREATE SET [DBCS_KOR_CHAR_9998082__20040430].[#SERVER#G
SET2#ア箍」#REL#SSG1000000001#IMS3#&@SSG1] AS
'{[#SERVER#G CALC#ア箍」#REL#SSG1000000001#&@SSG1]}'
SET [DBCS_KOR_CHAR_9998082__20040430].[#SERVER#G
SET2#ア箍」#REL#SSG0000000002#IMS3#&@ssg] AS
'{[#SERVER#G CALC#ア箍」#REL#SSG0000000002#&@ssg]}'
SET [DBCS_KOR_CHAR_9998082__20040430].[IMS1チョヌミ]
AS '{{[チョヌミ].[GEO].[All
Geography].[423A#&@ネ」チヨ]}}' SET
[DBCS_KOR_CHAR_9998082__20040430].[IMS1チヲヌー]
AS '{{[チヲヌー].[MKT].[All
Product].[0#&@ヌユー·ステタ蘊}}'
SET [DBCS_KOR_CHAR_9998082__20040430].[IMS1ア箍」]
AS '{{[ア箍」].[REL].[0#&@クホ_ー·襍ヌエツ_ステー」].[M013#&@タフオソヌマエツ
ソャキハ
ヌユー·4エ゙
2003].[S019#&@ヌミア·10エ゙
2002].[Q022#&@ウサケォケン
7エ゙ 2002].[P024#&@エ゙ 5エ゙
2002]}}' MEMBER [DBCS_KOR_CHAR_9998082__20040430].[Measures].[#RANK#IMS1#チョヌミ#&@rank]
AS 'RANK(([チョヌミ].[GEO].CURRENTMEMBER),
ORDER({{[チョヌミ].[GEO].CURRENTMEMBER.SIBLINGS}},
([Measures].[ー。ト。
ー「タレ エレナヘ]),
BDESC))', SOLVE_ORDER = 1000, FORMAT_STRING = '#' SET
[DBCS_KOR_CHAR_9998082__20040430].[IMS1MEASURES] AS '{{[Measures].[
ー。ト。]}}' SET
[DBCS_KOR_CHAR_9998082__20040430].IMS1SLICE1 AS
'{[IMS1チヲヌー]}' SET
[DBCS_KOR_CHAR_9998082__20040430].IMS1SLICE2 AS
'{[IMS1ア箍」]}'

I am attaching the screenshots of the query and error thrown in the
MDX Sample Application

Am I missing something? If not is there any workaround?

Thanks in advance for your help...

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.