Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I'm scratching my head over this. The script loads 6 fields from QVD files into Table1. Next, it loads 100 more rows from a BIFF file into Table2, with the same field names. NOCONCATENATE is specified for the second load.
An interim step modifies the data in Table2, leaving it with the same 6 field names.
Finally, it uses CONCATENATE (Table1) LOAD * RESIDENT Table2 to merge the two tables.
The problem? This last LOAD concatenates the data back onto Table2, even though the script specified "CONCATENATE (Table1)".
Why would QlikView insist on concatenating data to a table different from the one that is specified? I have a workaround (add all the interim processing into the second load statement, making it concatenate to Table1), but I need to understand what is causing this.
i am having the same issue. The Concatenate load will insist on loading onto itself much like yours. Have you found a better solution or the reason for this?
Hi,
I had the same problem and just by switching the order the problem was resolved. I have no explanantion for this.
So instead of CONCATENATE (Table1) LOAD * RESIDENT Table2 ,
try CONCATENATE (Table2) LOAD * RESIDENT Table1
I have noticed the same thing as Kristof and when I had this problem I just had to flip the order and all of a sudden it worked.
Thank you both for replying. I'll try this next time I encounter the problem.
James