Re: Problems distinguishing member keys

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Ohjoo Kwon (ojkwon_at_olap.co.kr)
Date: 03/01/05 

Date: Wed, 2 Mar 2005 02:38:18 +0900

Well... I think you can point out the member uniquely.

Actually I don't understand how another member can have the same member key.
At least the members at [Territory] level must have unique member keys at
the level, if you can reference them in format of [Level].&[Member Key].
Here I guess the member keys are not unique at the level. If then, you can
reference it uniquely by adding its ascendant as following.

[Territorio].currentmember IS [Territorio].[...].&[_0]

Ohjoo Kwon

"MJ Dias" <mjsd@netc.pt> wrote in message
news:fb3120fa.0503010917.57088ce7@posting.google.com...
> Hi,
>
> I'm implementing a cube security using Cube Cell Security Dialog Box.
> In the role I'm working on, I want the users to see only one of the
> members of dimension Territory.
> This member has the following Member Key: [Territory].&[_0]
> So I use the MDX [Territorio].currentmember=[Territorio].&[_0]
> But there is another member of this dimension with the Member Key:
> [Territory.&[0] , and when I test the role, I have access to both of
> them!
> It seems that it can't distinguish the two member keys.
>
> Does anyone knows why this happens?
>
> Thanks in advance,
>
> Maria