Different values in an original excel file and in qvd - why?

[#1]

Hello,

I have the following problem:

in excel file i have a column named gpn.

GPN is a calculated column, but in excel it appears as a result of calculation.

So in this column i have value 5.6 for some row. Why in qvd this value turns to be different?

In qvd this value turns to be 4.75....

Thanks a lot!

[#2]

Ok, can we fix it somehow while loading to qvd?

נשלח מה-iPhone שלי

ב-9 בנוב 2012, בשעה 20:20, Gysbert Wassenaar <qcwebmaster@qlik.com> כתב/ה:

QlikCommunity

Re: Different values in an original excel file and in qvd - why?

created by Gysbert Wassenaar in Development (QlikView Desktop) - View the full discussion

The precision of the numbers in the csv file seems to be higher than excel can handle. So if open the csv file in a text editor and compare the value with qlikview you'll see the same numbers. But afaict excel just displays less decimals. It's a display problem only. The data in the csv is the same as in qlikview as far as I can tell.

Reply to this message by replying to this email -or- go to the message on QlikCommunity

Start a new discussion in Development (QlikView Desktop) by email or at QlikCommunity

© 1993-2011 QlikTech International AB Copyright & Trademarks | Privacy | Terms of Use | Software EULA

[#3]

Hi,

I understand, but how can we create a situation that sum in cvs will be equal to sum in qvd?

CSV is a result of stored procedure , may be we can deal with decimal resolution there? What resolution has to be in csv? 2 places after point?

thanks

[whiteline]

Hi,

How do you get the csv, with QV store statement ?

[#5]

Hi, csv file is a result of stored procedure which runs in sql server.

So, stored procedure includes joins between 30 tables and exports csvs.

These csvs should be loaded to qvds.

Thanks

[whiteline]

I think it's better to compare the values from qvd with the real values from csv (not that excel shows).

You could also store the result of total sum aggregation of that data from sql server.

[#7]

Hi,

thank all, I found a solution.

If I multiply the problematic column for 1000 and the while loading I divide for 1000, the value is correct.

Thanks again.