Hiding Parameters

I have a popup window which shows the report. I don't want user to modify
the parameter of the displayed report.
how can i hide the parameter list.
I am familiar with rc:ToolBar = false while invoking the report how can i
disable parameter from being changed
thxtry setting the parameter(s) to be "Hidden" in the report properties applet
"nkg" wrote:
> I have a popup window which shows the report. I don't want user to modify
> the parameter of the displayed report.
> how can i hide the parameter list.
> I am familiar with rc:ToolBar = false while invoking the report how can i
> disable parameter from being changed
> thx
>
>|||thx
"Carl Henthorn" <CarlHenthorn@.discussions.microsoft.com> wrote in message
news:41752B0A-DB95-4B08-A3E3-04F51EA97686@.microsoft.com...
> try setting the parameter(s) to be "Hidden" in the report properties
> applet
> "nkg" wrote:
>> I have a popup window which shows the report. I don't want user to modify
>> the parameter of the displayed report.
>> how can i hide the parameter list.
>> I am familiar with rc:ToolBar = false while invoking the report how can i
>> disable parameter from being changed
>> thx
>>

hididng calculated measures in the cube browser window

hi i am currenly using analysis serivces 2005 for making cubes.

my problems are 2 fold

1)the list of calcualted measures is around 35 so when i go to browser window in the cube they actually give a very bad look.Can i make any folder within which we can keep all the calculated measures and then drill down according to the requirement. OR if i can divide all the calculated measures according to the need-- say "primary sales" calculated measure folder contains all the calculated measures that fall under that category and simlarly "order daily" contains all the calculated measures that fall under its category.

2)the end user will be accesing the cube using BIP now in the cube Dimension we can discriminate among the hierarchy and attributes by there default symbols but when we actually see it in the BIP window we cannot distinctly identify which is a attrribute and which is a hierarchy,which might confuse the business user.

kindly reply asap

cheers
Sid
..u can mail me at sidhuvirgoster@.gmail.com(for answer and further clarification of question)

Unfortunately I don't have a lot of good news for you.

1) you can put measures into display folders, there is a button on the toolbar of the calculations tab called "Calculation Properties" which lets you set this. (the button looks like a properties window with a little yellow hand over it)

2) Unfortunately BIP uses OWC which was written before AS2005 existed and it is not aware of attributes or hierarchies, it treats them all as just dimensions. There is no way around this and MS has discontinued development of OWC so it will not change in the future. And in relation to your first point, OWC is not aware of display folders either so all your measures will still be displayed in a big long list.

All I can suggest is to have a look at some of the other 3rd party browsers, Mosha has one of the most comprehensive lists around at www.mosha.com/msolap

|||About 2.

Why is this so important for the end user to see where the attribute hierarchy is? As far as i understand the model, an attribute hierarchy is still a hierarchy, which consists of one level and represents just a plain list of members of certain entity (attribute). They are visible to the end user by default, but the designer can make them invisible, leaving just those hierarchies, which do not confuse the user.

For the cube developer - yes it is more important to see what comes from what.|||

I agree that end users should not really care about the difference between attribute hierarchies and other hierarchies. And typically if I have "Month" in a user defined hierarchy I will hide the attribute hierarchy so they don't see the same thing twice. One problem I have seen is situation where two different dimensions have attributes with the same name.

eg.

[Date].[Financial] and [Organisation].[Financial] would both show up as just Financial in OWC

or [Ship Date].[Month] and [Order Date].[Month] would both show up as Month

The only real work around if you need to use an older client (like OWC) is to make sure that the levels/attributes that the users see have unique names (eg [Ship Date].[Ship Month], [Order Date].[Order Month])

hide warning from query analyser

When I renaming tables,columns below message comes to Query Analayaser
Result Window.
Is there any way to hide it,
because this may hit performance if there are 1000's of columns updated
Thanks
Caution: Changing any part of an object name could break scripts and stored
procedures.
The COLUMN was renamed to 'F28'.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The COLUMN was renamed to 'F27'.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The COLUMN was renamed to 'F26'.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The COLUMN was renamed to 'F31'.Did you try SET ANSI_WANRINGS OFF? I forget the list of warnings that this
suppresses, I know it's not all of them...
"Abraham" <binu_ca@.yahoo.com> wrote in message
news:OP9FBW1ODHA.3700@.tk2msftngp13.phx.gbl...
> When I renaming tables,columns below message comes to Query Analayaser
> Result Window.
> Is there any way to hide it,
> because this may hit performance if there are 1000's of columns updated
> Thanks
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F28'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F27'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F26'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F31'.
>|||that one's a raiserror, so no. Why would performance of an object rename
process be a concern?
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:Oj3WJb1ODHA.704@.tk2msftngp13.phx.gbl...
> Did you try SET ANSI_WANRINGS OFF? I forget the list of warnings that
this
> suppresses, I know it's not all of them...
>
> "Abraham" <binu_ca@.yahoo.com> wrote in message
> news:OP9FBW1ODHA.3700@.tk2msftngp13.phx.gbl...
> > When I renaming tables,columns below message comes to Query Analayaser
> > Result Window.
> > Is there any way to hide it,
> > because this may hit performance if there are 1000's of columns updated
> > Thanks
> >
> > Caution: Changing any part of an object name could break scripts and
> stored
> > procedures.
> > The COLUMN was renamed to 'F28'.
> > Caution: Changing any part of an object name could break scripts and
> stored
> > procedures.
> > The COLUMN was renamed to 'F27'.
> > Caution: Changing any part of an object name could break scripts and
> stored
> > procedures.
> > The COLUMN was renamed to 'F26'.
> > Caution: Changing any part of an object name could break scripts and
> stored
> > procedures.
> > The COLUMN was renamed to 'F31'.
> >
> >
>|||I don't know of any way to turn off this message.
> because this may hit performance if there are 1000's of columns updated
If you are frequently renaming lots of columns then maybe you should rethink
whether that is really the best solution. I can't think of a reason why you
would want to do this regularly.
--
David Portas
--
Please reply only to the newsgroup
--
"Abraham" <binu_ca@.yahoo.com> wrote in message
news:OP9FBW1ODHA.3700@.tk2msftngp13.phx.gbl...
> When I renaming tables,columns below message comes to Query Analayaser
> Result Window.
> Is there any way to hide it,
> because this may hit performance if there are 1000's of columns updated
> Thanks
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F28'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F27'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F26'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F31'.
>