Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

PEEK giving bad data at large numbers

Hi I am using PEEK on a table with 10 million rows , and its giving me wrong data

??

11 Replies
Anonymous
Not applicable
Author

Problem is that its confidential and I am not allowed to do that. I would have to do quite a bit of stripping...

cwolf
Creator III
Creator III

That means, your field is a mixed value field. It contains not only numeric values but also alphanumeric values.

And thats why you get 3 different results:

Max(DiagnosisObjectID) ==> Maximum of the numeric values

Max(Fieldvalue('DiagnosisObjectID',RecNo())) ==> it's the same as max(DiagnosisObjectID), but I think you will see here a "?" as result, because in this case QlikView don't know how to interpret it (numeric or alphanumeric).

ORDER BY DiagnosisObjectID DESC ==> Maximum of ASCII values

and with MaxString(DiagnosisObjectID) you will get another differnt result.

Normally Max(DiagnosisObjectID) should be the fastest solution of all, but in the case of mixed values QlikView has at first to filter out the numeric values, before it can determine the max value of them and thats why it takes a few of minutes.

Maybe most of your values are filled with blanks on the right or left side.