Date fields incorrect during load in Qlikview 10

[#1]

Since installing Qlikview 10 (desktop and server), reloading the standard data load script that loads the data from a progress database through the odbc connection gives the date fields in the incorrect format.

After loading the script to create the qvd files in Qlikview 10, loading these qvd files will give the data formats as for instance 40353.000776.

Loading the same script in Qlikview 9 will give the date fields in the correct format (displayed as for instance 01-01-2010).

Did something change in Qlikview 10 which might cause this change?

Another issue that we have is that since Qlikview 10 when loading all tables at once from the progress database results in an error that too many cursors are open. This does not occur in Qlikview 9, I assume this has to do with the load optimization of Qlikview 10, but is there a way to go around this? Currently I just put a disconnect and reconnect to odbc in the script after every 40 tables, so the error no longer occurs.

[#2]

I have the same problem with dates in version 10 (it worked in version 9), the problem occurs for date like yyyy-mm-jj hh:mm:ss.ccc

I dont' know yet if this is a bug but in my case I fixed it by adding thisin the LOAD section

Date(Left(MYDATE,8)) AS MYFDATE

.

[#3]

I just asked the question to Qliktech:

RESOLUTION:
This is a known bug.
Bug ID #34200 - Dates values formatted as timestamps.

It has status fixed so I am pretty sure you won't see the problem in v10 service release 1, which is planned to be released 15th December.

[#4]

Hi I installed Qliview 10 SR1 yesterday to resolve this issue and it still seems to be the same.

reloading the same qvws through version 9 works fine.

anyone else had this problem?

[#5]

I installed Qliview desktop 10 SR1 then reloaded my documents and all works fine now so I confirm the problem known as "Dates values formatted as timestamps" has been fixed

[#6]

I can confirm that this is still not working on qv10 sr1 in my apps.

dates are being pulled through as 20379.0000000 rather than 2007-12-02 00:00:00

any help?

[#7]

How do you display dates in your script ?

I remember I have to replace a date#() function by date() in a script between the version 9 and the version 10

[#8]

Should be fixed for DB2. For me, it works. (QV10 IR was not workin)

You should be able to workaround like this:

date(floor(date_field))

You get a date, that could be linked with internal calendar and so on.

[#9]

I have the same situation as you do. If I load the data through odbc with qv10 sr1, it loads dates as 20379.000000 etc, however if I then load the stored qvd in another qvw, it is recognized correctly as a date and all my date scripts now work fine.

I also tried the floor solution and this also solved it in qv10 sr0.

[#10]

It is simple.

This is a bug. You have to report it to QV-Support, so they can fix it again. Some DBs (ODBCs) are just fixed in SR1, obviously not all. So report it and wait for SR2.

For now, all have to workaround with floor(). This works really well untill you come to conditional intervallmatch(), then it gets harder, but still floor is helping.

Solution with load over QVD also could be a workaround. A new one for me. I think this would take more time and harder to come back, when this problem is fixed.