Marcus Sommer <span class="icon-status-icon icon-mvp" title="Mvp"></span> wrote:
Nope, it hasn't - it's a complete different layer. But again what's the aim? I have the feeling that you runs in a wrong direction ...
Ok... I have columns that named by years (2014, 2015, 2016 etc). I have slider where I can select years I want to have report for. So I need to sum all columns that are selected in slider. I found solution how to make this sum, but by some reason the ".GetPossibleValues(1000)" doesn't come up with the same number of possible items as the "GetPossibleValues" Function in the report. Trying to figure out what is wrong...
I think I cracked it. Basically I couldn't find sum function, so I had to simulate it:
for i=0 to val.Count-1
dSum = dSum + cDbl(val.Item(i).Text)
don't go in that direction.
Forget about VB at all in this case.
Instead post a small sample application and your expected result in case of some selections.
Maybe you can use a crosstable load to convert your multiple year columns into one year field and use this one to perform your selections.
There surely are many possibilities to meet your requirements, none of them needing VB scripts.
hope this helps
Thank you, for all your response.
Here is the Sample file. In real Data source I have about 100 columns, should I create 2 table to keep those years separately for Xtable? and most important hot to properly create it? I saw few post about this, but still don't completely understand it.
SAMPLE1.qvw 149.5 K