topic Re: Same application and excel files different reload result on two different machines (QV desktop) in QlikView

Same application and excel files different reload result on two different machines (QV desktop)

joseph_eftamand — Sat, 16 Nov 2024 05:04:06 GMT

Hi All,

We have an application that reloads on a set of excel files. We have noticed that there are slight differences between machines after the same reload of data. On one machine the application shows data at the start of the week for that week while the other app (on machine 2) doesn't but seems to catch up after a few days. Is there any known setup for each machine that could effect how the app is interpreting time related fields that would explain this? There doesn't seem to be anything apparent as applications are identical in every way. Same version of QV is used on both machines 12.0.2 SR5.

Thanks,

Joseph

Re: Same application and excel files different reload result on two different machines (QV desktop)

hopkinsc — Tue, 04 Dec 2018 10:02:03 GMT

Hi,

Just to confirm your issue, you have the same QV version on both machine, exactly the same QVW (so no script or chart differences), both machines are reloading exactly the same excel files but there are differences in data after both reloads finish?

is that correct?

Re: Same application and excel files different reload result on two different machines (QV desktop)

joseph_eftamand — Tue, 04 Dec 2018 10:08:23 GMT

That's exactly it. It's in specific charts that are missing certain records in one but not the other. But as you say no difference in script/charts/data.

Re: Same application and excel files different reload result on two different machines (QV desktop)

hopkinsc — Tue, 04 Dec 2018 10:18:27 GMT

I don't know what to make of that as i would say it isn't possible.

Are both machines on the same timezone?

Have you tried copying the QVW from machine 1 to machine 2, check the data first, then reload and see if the data has changed?

Are you sure that the excel files are being read from the same location on both machines (one isn't in a test/dev environment)?

Sorry, these might seem like silly questions, but from experience mistakes are easily done 🙂

Re: Same application and excel files different reload result on two different machines (QV desktop)

joseph_eftamand — Tue, 04 Dec 2018 10:21:27 GMT

No I know where you're coming from!

The app and excel files are small enough that we can send them by email so we test with the same apps and files.

The two machines are in the same time zone.

It's very strange.

Re: Same application and excel files different reload result on two different machines (QV desktop)

Colin-Albert — Tue, 04 Dec 2018 10:41:35 GMT

The two machines are using QV desktop - is the same user logged onto each machine?

Re: Same application and excel files different reload result on two different machines (QV desktop)

hopkinsc — Tue, 04 Dec 2018 10:42:35 GMT

Is there section access applied?

Re: Same application and excel files different reload result on two different machines (QV desktop)

joseph_eftamand — Tue, 04 Dec 2018 10:46:57 GMT

No there are two users. The two desktop versions are licenced.

Re: Same application and excel files different reload result on two different machines (QV desktop)

joseph_eftamand — Tue, 04 Dec 2018 10:48:03 GMT

No Section Access applied

Re: Same application and excel files different reload result on two different machines (QV desktop)

jensmunnichs — Tue, 04 Dec 2018 11:03:10 GMT

Is there still a difference when user 2 logs in and reloads on user 1's machine?

Re: Same application and excel files different reload result on two different machines (QV desktop)

joseph_eftamand — Tue, 04 Dec 2018 11:06:51 GMT

The difference appears to be related with the Today() function used to create a loop which pulls data. Today() is calculated as yesterday by machine 2 while machine 1 is today. Reload time on the front end is the correct date time.

Re: Same application and excel files different reload result on two different machines (QV desktop)

hopkinsc — Tue, 04 Dec 2018 12:07:44 GMT

So if you create a text box and use the formula =today() in it you get yesterdays date?

Re: Same application and excel files different reload result on two different machines (QV desktop)

joseph_eftamand — Tue, 04 Dec 2018 12:21:25 GMT

Today() is used in the script saved result is saved as variable vMaxDate and used in a loop. Is wrong only on one machine. Works fine on my own. As a workaround I replaced Today() with Now() and it seems to work but can't find any reason why Today() wouldn't work on that machine.

Re: Same application and excel files different reload result on two different machines (QV desktop)

hopkinsc — Tue, 04 Dec 2018 12:30:45 GMT

Hmm that's a strange one. I'm glad you have a workaround though.

Re: Same application and excel files different reload result on two different machines (QV desktop)

jensmunnichs — Tue, 04 Dec 2018 12:38:36 GMT

Could it have something to do with the timer mode for the Today() function? That seems to be the problem other people were having.

Re: Same application and excel files different reload result on two different machines (QV desktop)

Colin-Albert — Tue, 04 Dec 2018 12:38:42 GMT

What happens if the two users login and run the report on the sme machine?

Is there a difference in the date settings on the two machines?
What date do you get from running "date" at a command priompt on each machine?

Re: Same application and excel files different reload result on two different machines (QV desktop)

joseph_eftamand — Tue, 04 Dec 2018 13:36:05 GMT

We each have a licenced QV desktop on our personal machines. There is nothing in the app that would impose any restrictions on users. In any case we can't really test the user login as we are in different locations.

The date in the command prompt is correct for both though!

Thanks for your input!

Re: Same application and excel files different reload result on two different machines (QV desktop)

joseph_eftamand — Tue, 04 Dec 2018 13:43:45 GMT

As far as I can tell this must be it. It also explains why the workaround works. Thanks for the help!!