Calendar Date - internal link QV10

[#1]

Hallo,

I have a big problem with QV10. I just set up a testserver and just updated my QV9.5-Applikationions. Everything was just fine and ultra fast. Good job a this point by the way. But then I stuck with a big problem...

Calendar-Date-Fields did not link correctly:

Calendar: Fact-Table:
Date Year Date Price
01.01.2010 2010 01.01.2010 $10

Should be:
Date Year Price
01.01.2010 2010 $10

But got to:
Date Year Price
01.01.2010 2010 -
01.01.2010 - $10

In QV9.5 I didn't need to format my date from fact-table. After port to QV10 and notice of this problem I did so and formated both "date"-fields to date() but that did not the trick. So I tried text(date()) and that did it.

But now I have a new problem. I use Intervallmatch on some of my apps. So now I have to use Intervallmatch on text()-formated field, what is impossible. So I could think of use num() but this one is to "hot" for me. "num(01.01.2010)"

Someone has same problem or a solution for me?

Greetings,
Jonas

[#2]

Hallo,

I tried some more things like hash128() and others. But I am not able to get intervallmatch to work. I have 3 datefields here. Date in calendar and 1 start-date and 1 end-date so intervallmatch have to compare all these 3 fields. It just doesn't work. QV10 is not able to "see" that date(01.01.2010) is the same as date(01.01.2010).

I just don't get it :-(.

Greetings,
Jonas

[#3]

I have made an example, so you can see what I mean. QVW is linked...

ODBC 32 and 64 tested. QV9.5 and QV10 Document tested. And others.

To always format my date-keys as text() is not that good option for me 😞 . Suprisingly I got my Intervall match to work with all fields formated date(). Just still didn't get that bug.

By the way... we use AS400 DB2 IBM iSeries ODBC.

Greetings,
Jonas

[hic · Accepted solution]

I looked at your application and it seems as if the dates really are timestamps - same date but different minutes and seconds. This is why the values do not link. I have the following values:

02.10.2010 00:00:00
02.10.2010 00:01:23

Try Date(Floor(DATUM)) and it will probably work.

Cheers

Henric

[#5]

I'll try your solution and I can imagine that it should work that way. But the strange thing is... my dates from database ARE dates and not timestamps. Till QV9.5 SR6 I never had problems on this one. Even not formating my dates from source did it. In past I had to do nothing and it worked like it should be.

Now the new scriptenvironment seperated from client itself leads to that problem. Could be worse I think but I have to reengeneer all links in all my apps for internal date to calendar. 😞 .

[#6]

Hello

Excatly the same problem here. My data come from and iSerie.

I migrate from QV9 to QV10 and i have the problem with all my calendar scripts.

My date key don't match any more. as you can see it seem that there is 00:01:23 in my date field !!!

Is the floor fonction resolve the problem with QV10 ?

Thanks

[#7]

Hey Marlot,

yes, floor did the job. I had to rewrite alle my stuff. Was really disapointing to see QlikView getting another Problem with iSeries. Now not just OleDB-Driver doesn't work at all, but even ODBC has it's problems :-(.

IBM OleDB doesn't work at all

IBM ODBC has a date-format-problem (floor can fix it)

If you use an intervalmatch on datefilds you have the biggest problems. Everytime I use if or SET on an date-field in QV10 I am scrupling.

Because I had other problems with a firebird x64 ODBC we downgraded on QV9 again. It seems there are more then one Problem with the new scriptengine. 😞 Firebird driver even totaly kills QV10 if you start dataimport.

Greetings,
Jonas

[#8]

Thanks for your help. Do you call the support for this issue ?

I downgrade too in QV9 for loading the data !!!

Marlot

[#9]

Hallo,

Henric Cronström (hic) just gave me this advice. He's from QlikTech I think. So I hope they look at this problem.

But it would not be the worst idea to tell support about this matter, so they have a closer look. I have not planned so. Perhaps you can make this call.

Greetings,
Jonas

PS. our dates are NO timestamps. QlikView make this mistake. We load DATE-Field and get a Timestamp-Field in QV10. It is always 00:01:23 ... for all Dates.

[#10]

Have you tried to modify the TimeStampFormat not to include seconds ? Maybe it is less work than adding floor() functions everywhere.

-Alex