Decimal places reduction on unoptimized qvd load

[#1]

Hi

Any one knows why QlikView reduces de number of decimal paces in floating point fields during unoptimized load of qvd and not, when load is optimized . (I'm using QV 10 SR3 64 bit edition)

Example:

XX:

LOAD ...,

          FloatingPontField,

          date,

          ....

FROM '..\MyFile.qvd' (qvd);

LET x= Peek('FloatingPontField', 0, 'XX');   ///  -->> x= 234.23477777777

---------------------

BUT

XX:

LOAD .....,

         FloatingPontField,

         year(date),    /// this function causes unoptimized load

         date,

         .....

FROM '..\MyFile.qvd' (qvd);

LET x= Peek('FloatingPontField', 0, 'XX');   ///  -->> x= 234.235

----------------------

And, Is there any way to tell QlikView, the number of expected decimal places, for floating point numbers in case of unoptimized loal?.

In my case I need more decimals than those 3 loaded.

Thanks in advance.

Regards

Walter

[Anonymous · Accepted solution]

Looks like a bug to me, but just in case try something like this:

num(FloatingPontField,'#,###.###########') as FloatingPontField

[#3]

Michael

Thanks that works.

Still would be nice to know why, the difference between load optimized and unoptimized makes this change, in my case was causing, data comparision errors and giving wrong information, because is used to match ranges of values with 5 or more decimals in presission.

Regards

Walter

[Anonymous]

Good to know it helps.  As for "why" - only QlikTech can answer.  I'd call it a bug.