Reg: ADOMD Connection With multi language support

I have a SQL Server AS 2005 Database with multi language support. Through Analysis Service browser if i change the language iam getting the selected language data.

In My web application by using ADOMD I need to fetch different languages data. How can get the different languages data?

In the Sql Server Reporting Sevice also i need get the different languages data.If any body knows about this can you please help me.

Regards

Hanu

Moving the thread to the more appropriate forum.|||

Try setting the Locale Identifier connection string property to the numeric identifier of the locale whose language you want to see. For instance, if you connect to the Adventure Works cube with Locale Identifier=1036 then you'll see the French translation of the cube.

HTH,

Chris

Reference for SSIS "C-like" script needed

Consider the Conditional Split task. I can use a C-like language to create statements such as

Ltrim ([Col1] =”A”) ||Ltrim([Col1] =”B”)

This sure ain’t VB-like and the list of functions in the upper right-hand pane of the task(“expression editor”) does not help me construct such statements.

Where is the reference manual describing this language?

TIA,

Barkingdog

P.S. I have found fragments in BOL but the info does not seem complete and the BOL topic fragmentation impedes learning.

P.P.S.Why MS uses this language instead of VB.NET, which they use in their Script tasks, is beyond me.

A few hours of looking around gave me this pointer:

http://msdn2.microsoft.com/en-us/library/ms141827.aspx

|||

>P.P.S. Why MS uses this language instead of VB.NET, which they use in their Script tasks, is beyond me.

One of the key reasons is that languages such as VB.Net, or SQL for that matter, include flow of control and procedural constructs which would be unsuitable for use in an expression language. So does C, of course, but it is easier to create a subset of the C grammar without those constructs.

I used to worry that the expression syntax would be a real problem for folks, but I have to admit that (a) most people appear to be using very simple expressions and get the hang of it pretty quickly and (b) those that do need complex expressions are on the whole able to get to grips with the syntax, with the help of the reference you found.

I'd be interested to hear other opinions, of course ...

Donald