Reload problem after update QV from v.10 SR4 to v.11.2

[#1]

Hi all,

after updating QlikView, I encountered a strange reload problem.

Specifically, the function involved is the following:

Table1:
LOAD
     MaxString(Column1)
RESIDENT Tablex
WHERE IsNull(Column2)=-1 OR Column2 >= '100'
GROUP BY Column4, Column5

Running this script with version 10, I get this (by log):

19/07/2013 11.24.27: 0370      Geografia:
19/07/2013 11.24.27: 0371                          LOAD
19/07/2013 11.24.27: 0372                                    MaxString(Column1) as Column1
19/07/2013 11.24.27: 0373                          RESIDENT Tablex
19/07/2013 11.24.27: 0374                          WHERE IsNull(Column2)=-1 OR Column2>= '100'
19/07/2013 11.24.27: 0375                          GROUP BY Column4, Column5
19/07/2013 11.24.27:                     1 fields found: Column1, 6.802 lines retrieved

Instead, running this script with version 11.02, I get this (by log):

19/07/2013 11.24.27: 0370      Geografia:
19/07/2013 11.24.27: 0371                          LOAD
19/07/2013 11.24.27: 0372                                    MaxString(Column1) as Column1
19/07/2013 11.24.27: 0373                          RESIDENT Tablex
19/07/2013 11.24.27: 0374                          WHERE IsNull(Column2)=-1 OR Column2>= '100'
19/07/2013 11.24.27: 0375                          GROUP BY Column4, Column5
19/07/2013 11.24.27:                     1 fields found: Column1, 6.650 lines retrieved

The source database is obviously the same, it isn't changed.

I tried searching about function MaxString(), but for now I haven't found anything.

Can someone help me?

Thanks in advance.

[Anonymous]

Got back to it, out of curiosity...

If you want the data to be numeric rather than text, and still in hex format, it is possible as well:

SQL SELECT

   ...,

       num#(IDAFF, '(hex)000000') as IDAFF

FROM dbo.AFF
...;

[#3]

Hi Michael, thank you for your interest.

With the Text() function I solved the problem.

The data of IDAFF column have a 100% uniqueness index and loading data of AFF table is ok.

But...I am worried about having to go and check all the database fields that are declared as hexadecimal.

I think that a normal behavior of QlikView shouldn't lead to these checks. Isn't it?

This involves changing all the load script involving hexadecimal fields. And the database is too large.

What do you think about?

[Anonymous · Accepted solution]

"What do you think about?"

I don't think about it... 🙂

Well, if it were my problem, I'd first checked the other fields (there shouldn't be too many that may be hexadecimal), and, second, I'd reported it to the QlikTech support.

Regards,

Michael