topic Re: [Bug] Bug with set analysis in QlikView

[Bug] Bug with set analysis

Mon, 21 Jul 2014 08:04:54 GMT

Hello,

I think i have a bug with Qlikview when I am using sum().

Here a simple test with the DBMS :

Here the results with QlikView :

The source is the same DBMS.

Here is my script :

SET ThousandSep=' ';

SET DecimalSep=',';

SET MoneyThousandSep=' ';

SET MoneyDecimalSep=',';

SET MoneyFormat='# ##0,00 €;-# ##0,00 €';

SET TimeFormat='hh:mm:ss';

SET DateFormat='DD/MM/YYYY';

SET TimestampFormat='DD/MM/YYYY hh:mm:ss[.fff]';

SET MonthNames='janv.;févr.;mars;avr.;mai;juin;juil.;août;sept.;oct.;nov.;déc.';

SET DayNames='lun.;mar.;mer.;jeu.;ven.;sam.;dim.';

OLEDB CONNECT32 TO secret_chain;

LOAD annee,

"nb_jours_realise";

SQL SELECT *

FROM palan."public"."v_projet_charges_agent";

Here is the set analysis I use : sum(nb_jours_realise)

Is there any cache to empty ? Should I reinstall QlikView ?

Thanks,

Re: [Bug] Bug with set analysis

alexandros17 — Mon, 21 Jul 2014 08:10:04 GMT

I do not think there is any bug, check better data,

I see that you have done a group by while in qlik view there is a simple sum ?

Let me know

Re: [Bug] Bug with set analysis

MK_QSL — Mon, 21 Jul 2014 08:11:30 GMT

Can you load your data in excel file please?

Re: [Bug] Bug with set analysis

Mon, 21 Jul 2014 08:18:13 GMT

Hello,

Well, I have add "annee" as a Dimension. So I consider that it implies "annee" as a part of the group by.

I don't know if you have noticed but for 2008, numbers are good... but not for the others.

Re: [Bug] Bug with set analysis

MK_QSL — Mon, 21 Jul 2014 08:21:55 GMT

Kindly load your sample data in excel format.. thanks

Re: [Bug] Bug with set analysis

alexandros17 — Mon, 21 Jul 2014 08:22:45 GMT

You're right there should not be differences between the 2 results but if therere are it means there is something wrong with data:

The first question is:

LOAD annee,

"nb_jours_realise";

SQL SELECT *

FROM palan."public"."v_projet_charges_agent";

why have you used " for the field nb_jours_realise?

Could you attach an example?

Re: [Bug] Bug with set analysis

Mon, 21 Jul 2014 08:27:52 GMT

Well, I haven't use quotes ", QlikView put it automatically because the field name contains underscores.

Re: Re: [Bug] Bug with set analysis

Mon, 21 Jul 2014 08:30:17 GMT

I am sending it (in CSV and Excel format).

Thanks,

Re: [Bug] Bug with set analysis

alexandros17 — Mon, 21 Jul 2014 08:31:35 GMT

try to load without quotes, verify (with a simple table - so no dimensions and expression) that numbers are aligned to the right (this means that qlikview recognise data as numeric)

Let me know

Re: Re: Re: [Bug] Bug with set analysis

MK_QSL — Mon, 21 Jul 2014 08:37:16 GMT

This is what I received in QlikView when I load your excel file...

Re: Re: [Bug] Bug with set analysis

Mon, 21 Jul 2014 08:43:05 GMT

I have reloaded the first request without quotes -> same result as before.

I have created a new simple table, without any dimension or expression -> does not show any data (there is only a grey rectangle).

I have create a new second simple table, with "annee" and "nb_jours_realise" as dimension -> I can see columns names, but the table is empty.

Re: [Bug] Bug with set analysis

alexandros17 — Mon, 21 Jul 2014 08:58:33 GMT

I'm trying to do an analysis:

1) When I load data from excel it seem all correct

2) settings are correct

The only difference is that you load data from an sql:

1) first try to load from excel and verify the result. if it is correct (as I think) the only problem could be the OLEDB CONNECT32 TO secret_chain; try with ODBC

Let me know

Re: Re: [Bug] Bug with set analysis

Mon, 21 Jul 2014 09:12:54 GMT

Yes you were right ! The results are correct when I use ODBC instead of OLEDB.

But can you explain where those differences are comming from ?

Thanks

Re: Re: [Bug] Bug with set analysis

alexandros17 — Mon, 21 Jul 2014 09:16:53 GMT

Probably because the Oledb driver is not the correct one!