Thursday, 10 September 2009

Keeping a Trace on things

I love QlikView. I love the way that I find new things all the time.

Occasionally, when I am very bored, I sometimes have a look in the help file for things that I am not familiar with. That is how I learned about Trace.

Trace is very cool in that it allows you to both comment your code and have those comments appear in the Script Execution dialog. It also supports variable use.

So, I could have a script like this:

For i = 1 to 10

Info:
Load
Information
From File$(i).qvd (QVD);

Next



In the past, I may not have been exactly sure where in the look I am without having to physically count the entries in the Script Execution dialog. Now, I can add a trace into the loop:

Trace Loading from file: File$(i).qvd;



And it will appear in the Script Execution like:

Loading from file: File1.qvd



What's more, it also appears in the script execution log file (you have to turn that on in the Document Properties - General - Generate Log File).

I wonder what interesting things that you might find in the help file?

2 comments:

  1. In order to enable a smooth automatic refreshing or our application we put the ErrorMode to 0.
    Then we have a masterapplication running, which scans through all logfiles, filtering whether there was an error (as per keywords).
    Using the TRACE along with usage a keyword we also enable to highlight some warnings to show up in the central file (like plausibility-checks on the amount of data loaded etc).

    ReplyDelete
  2. This comment has been removed by a blog administrator.

    ReplyDelete