Folks,

RE: v6.0.2. SQL Server 2008

1.       While building a calculated member from RED, on the  Adding  measures screen, checked Calculated measure Month to date

the following calculation string was entered by the RED:
'SUM(Filter([dim_pick_date].[pick cal month].members,[dim_pick_date].CurrentMember.Properties("pick_current_cal_mtd") = "Y"),[Measures].[a lbr cost])'
This caused browser to display vale of "#VALUE!" in the measure field

William manually entered the following calculation that did the trick

([Measures].[a matl cost],[dim_pick_date].[pick_current_cal_month].&[Current])

2.       Also the Non empty behavior drop down list is not populated

Hi,

Not your usual post...  

We're in the process of trying to push the use of Wherescape into a business unit that currently creates Perl scripts to write reports.  Each time there's a new requirement they have to create a new Perl script.  They're good at it but it does cost a bit and we're in the process of trying to put a realistic figure on that - something other than 'Eric can knock up a report in a day or two'

They accept that their current approach is not ideal and over time it should be cheaper to produce reports using Wherescape but they need to see some examples of where this sort of thing has been done before so that they can go to the bean counters and say the break even point is X, Y or Z

Does anyone have real-world examples of where this has happened?   I'd be particularly interested in any examples where the first set of reports cost X, including Wherescape, but the second set were  X/5 and a third were X/10 to illustrate the efficiencies of reusing the first development

Does sound a bit like a piece-of-string question but anything would help

Thanks, Tom