Change logs

Unfortunately, one of the things QlikView is not great at is version control. It can be really hard to see what has been done between versions of a document, and using the -prj folder feature can be extremely tedious and not necessarily helpful. So, this means that you, as the developer, need to maintain some discipline over version control.

To do this, ensure that right at the top of your script, you have an area of comments that looks something similar to this:

// Demo.qvw
//
// Roger Stone - One QV Ltd - 04-Jul-2015
//
// PURPOSE
// Sample code for QlikView Unlocked - Chapter 6
//
// CHANGE LOG
// Initial version 0.1
// - Pull in ISO table from Internet and local Excel data
//
// Version 0.2
// Remove unused fields and rename incoming ISO table fields to 
// match local spreadsheet
//

Ensure that you update this every time you make a change. You could make this even more helpful by explaining why the change was made and not just what change was made. You should also comment...