One of the strongest side of QlikView is the build-in powerful ETL layer that allows you to import data from various sources. Sooner or later QlikView developer have to load some old huge unique and extremely valuable ascii file that sometimes contains a few odd line feed (LF or \n) or carriage return (CR or \r) symbols. As a result strings are divided into subsequent rows.
You just can’t load it as delimited file directly into QlikView. The power of ‘transform step’ can’t help here too.
Nevertheless QlikView can easily handle it with a few tricks. I decide to write a detailed guide as there are pitfalls that must be explained carefully.