I am not aware of any Qlikview native functionality that compares to SQL cursor and recently I got a request to migrate an Excel macro to Qlikview not using VBscript. The macro examines rows whereas Qlikview typically deals with set as I understand. I finally came up the loop to check rows but it's rather inefficient ,i.e. 10,000 rows cost me over 20 mins on Server. Is there any other user case that applied different methodology?
I've recently done something similar. I would analyze the VBScript, breaking the transforms into "stages". I would create a series of QlikView documents. In the first, load the data from the source (CSV / Excel / SQL Server) using a load statement. Then perform incremental stages, reading, transforming and loading the data into resident tables. Then export the resulting tables in the required format (preferably output one QVD per table). In the next QlikView document, read those QVDs files in and display your graphs.
