Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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
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.
So if you create a text box and use the formula =today() in it you get yesterdays date?
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.
Hmm that's a strange one. I'm glad you have a workaround though.
Could it have something to do with the timer mode for the Today() function? That seems to be the problem other people were having.
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?
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!
As far as I can tell this must be it. It also explains why the workaround works. Thanks for the help!!