Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi there,
We have recently upgraded to QlikView 9 (9.00.7440.8 SR3 64bit) since the upgrade we are experiencing "Allocated Memory Exceeded Errors"
These errors seem to be specific to QlikView 9 (the models opens and runs perfectly in Version 8.5 (8.50.6261.5 64bit)
The error is being generated on even simple equations such as "avg(if(Year=vMinYr,[Stat Value])) "
Note: Fields [Year] & [Stat Value] reside in seperate tables linked by a common field. An mentioned the expressions are calculating successfully in Version 8.5
[Stat Value] is also an inputfield
Any help in this regard will be highly appreciated.
Hi,
I don't know exactly why you have this memory problem, nevertheless, I would suggest to change your expression by using set analysis (QlikView Reference Manual Book III, chapter 19.4) instead of using an "if" statement in an agregation function (which is very resource consuming), even in 8.5.
avg(if(Year=vMinYr,[Stat Value])) should become something like that :
note : I think the expression of your variable vMinYr should start with a = in the previous example.
I just have a doubt on the fact that Stat Value is an inputfield as I'd never test inputfield with set analysis before.
Hope it helps.
Regards
=Avg({$<Year={$(=vMinYr)}>}[Stat Value])
Hi,
I don't know exactly why you have this memory problem, nevertheless, I would suggest to change your expression by using set analysis (QlikView Reference Manual Book III, chapter 19.4) instead of using an "if" statement in an agregation function (which is very resource consuming), even in 8.5.
avg(if(Year=vMinYr,[Stat Value])) should become something like that :
note : I think the expression of your variable vMinYr should start with a = in the previous example.
I just have a doubt on the fact that Stat Value is an inputfield as I'd never test inputfield with set analysis before.
Hope it helps.
Regards
=Avg({$<Year={$(=vMinYr)}>}[Stat Value])
Hi,
I have tested and am pleased to confirm the issue seems to be resolved - many thanks for your assistance
Best Regards