I solved this playing around a bit, is a bugger
maxstring(Customers.timestamp) as MaxID
MaxID = peek('MaxID',0,CustomerMaxKeyLoad)
MaxID2 = 0x$(MaxID);
I then used the second variable to filter the reocrds in the database, probably a better way and if there is please let me know.
Hello Evgeny and everyone
This is very useful information and in my viewpoint a possible bug + error in QlikView not to be able to load timestamp (hex) from an SQL server without truncating important data.
Am very grateful to Evgeny for pointing this out as I am using the timestamp field from Microsoft Navision SQL to get the maximum date and id to be used for incremental updates on a daily basis. If the timestamp values were missing 0x, I would be getting the wrong maximum dates and ids all the time.
QLIKTECH - can you please reply to this post or perhaps give an explanation about why this particular case happens?
I don't know if this is going to help you, but there are expression formats for hex values, i did a test with the hex number posted here, but it returns me a number which doesn't look like a date
See the attached image and make your comments please
hex_numbers.png 4.0 K