I'm extracting data from a SQL database and to recognise new records for some tables I'm using the timestamp field. I realise this isn't a time but a binary field but there is nothing else I can use. For other transactional tables i have an Entry No. and this works perfectly.
When I get the max timestamp it returns a field like this 000000000003AA0D. I however cannot filter on this because in SQL the field looks like this 0x00000000003AA0D. So for some reason QlikView takes the 'x' away. I'm using maxstring(timestamp) to get the latest timestamp. If I use MAX it doesnt work.
So now I have to add in the 'x' to make this work, I saw there is a replace function but this doesn't work.
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?