it’s all about QlikView
Posted by Gilles on 10/02/2010 under How To | 
Be the First to Comment
Highlighting in UltraEdit: http://blog.birchroad.net/2010/01/26/ultraedit-wordfile-for-qlikview/ with thanks to the Birchroad Blog
Highlighting in Notepad++: http://guerrillabi.com/syntax_highlighting_qlikview with thanks to Guerrilla Business Intelligence
Posted by Gilles on 05/05/2009 under How To | 3 Comments to Read
In general performance is improved by moving the “problem” from application objects to the script driven database. This is often a trade off situation. Response time is enhanced and ad hoc capability is diminished. The recommendations below should not be seen as universally beneficial. Use them when they improve the general state of the application or when they make that little bit of difference that makes or breaks.
Cases:
1. Count ( Distinct ‘FieldName’)
2. If ( Condition(Text),…..)
3. Sum ( If (Condition, ‘FieldName’…))
4. If ( Condition, Sum(‘FieldName’)..)
5. If ( Condition1, Sum(‘FieldName’),
If (Condition2, Sum(‘FieldName’)……..
6. Sort text
7. Dynamic captions and text objects
8. Macro triggers ( “on change” )
Posted by Gilles on 19/01/2009 under How To | Read the First Comment
In many situations you have different sets of databases to connect to. In the real world you’ll probably have a development database, Quality Assurance databases and a production environment database. I can imagine when your Qlikview application is under construction or while testing you would like to switch databases very easily.
It’s relatively easy to create a simple switch with which you can switch between development and production connections. Let’s show an example:
SET vProduction= 0;
IF vProduction = 1 THEN
···ODBC CONNECT TO MyOracleDBProd (XUserID is *****, Xpassword is ****)
SET vDBName = ‘MyOracleDBProd‘;
ELSE Read more of this article »
Posted by Gilles on 15/01/2009 under How To | 2 Comments to Read
Putting comments in your scripts is good practice. It makes your scripts better readable and understandable for other users. In this post I’ll give you some tips about putting comments in your scripts.
As stated in my previous post about Tabs, I think it’s good to have some header comment. Put it on your first tab and make it something like below.
If you’ve got ODBC connections with scrambled userID and password make a comment that states the userID. This will help modifiers of your script immensly because they will know which account was used Read more of this article »
Posted by William on 14/01/2009 under How To | 18 Comments to Read
Sometimes when working with dates, it is better to keep the date fields outside the fact tables and create them in a table of their own. For instance, you may want to be able to see all dates, not only dates when something has happened. Below are two samples to create a master calendar. The first one contains a hard coded start year. The second one gets the start and end date from the fact table. This means you will always have all dates between the first and last date.
Posted by Gilles on 08/01/2009 under How To | Be the First to Comment
This post with tips is about scripting. How to set up your scripts initially and keep them maintanable and sustainable, so that other developers can find their way in your script and to set some sort of standard. One important thing to mention is that you’ll have to define your own set of standards. This is not the standard, but a start for a standard.
It’s good practice to split up your load script into several tabs. These split ups must be logical ofcourse. Below you’ll find a suggestion for the first three tabs.?
Read more of this article »
Posted by Gilles on 07/01/2009 under How To | Be the First to Comment
For a while now I have been looking for some best practices. How to set up a project and create a sustainable and maintanable solution, how to organise your scripts, how to create a good model, how a design should or could be. The Information that i will use comes from a presentation from Shima Nakazama a senior consultant at Qliktech Netherlands, ofcourse my own experiences and other stuff I’m able to find on the internet.
I’d like it to make it a serie of best practices posts. And I’ll start with scripting best practices. To keep things structured I will update this post with links to all best practices posts, see below