Qlik Community

Qlik Design Blog

All about product and Qlik solutions: scripting, data modeling, visual design, extensions, best practices, etc.

Announcements
Announcement: Certain actions are currently causing a Page Not Found error. This is a known issue and we are working with the platform vendor to investigate and resolve it.

Welcome to the QlikView Design Blog

Eighteen years ago I had just started a new job at QuikTech (no that’s not a typo) and my boss – one of the two founders – dropped a shrink-wrapped FoxPro database in my lap while saying: “You see, I have this idea about color coding information – green, white and gray. Can you see if you can achieve that with this database?”

 

At the same time, two other people in the company were given the same task but with other tools – Excel and a multimedia tool called Authorware. Neither of us succeeded very well, so we decided to call a really good developer that two of us knew from university and ask him if he could do something in C++.

 

A couple of months later we had the first version of QuikView, later renamed QlikView. It had list boxes and nothing else. No tables, no graphs, no aggregations, no numerical calculations. We sold these early versions to companies that needed logical visualization of data.

 

QV1 splash.png   QV1 list box.png

 

Many things have changed since, but the core in QlikView is still the same: The logical inference engine; the user selects a field value and QlikView answers by indicating which other values are implied by the selection and which are excluded. QlikView was different from all other tools on the market in that it was not a number-crunching tool – it was a tool for visualizing logical relationships.

 

QlikView is still today different from all other tools in this regard. In fact, the logical inference engine is what enables the user to explore data freely without predefined search paths, which is the core of Business Discovery.

 

The first two years with QlikTech, I had many hats. At the same time I was the project manager, the product manager, the R&D manager, the technical writer and the pre-sales consultant. But we did not use these labels then. We did not have clear roles and flexibility was important.

 

Since then, I have implemented numerous QlikView solutions and been heavily involved in defining new QlikView versions. Today, my responsibilities have moved toward communication about the product.

 

Hence, the QlikView Design Blog. Here, I and other “QlikTechies” will write about how to build QlikView solutions. We will write about scripting, visual design, extensions, server configuration, do’s and don’ts, etc. It will sometimes be very technical and sometimes not.

 

Please give us feedback on the content. Send us questions and suggestions. We are here for you. Welcome to the QlikView Design Blog!

 

Henric Cronström, Technical Product Advocate

16 Comments
Not applicable

Love the little history lesson!  It goes to show how powerful even just list boxes are given the ability to easily view logical relationships between data.

Also interesting to see all the currencies that no longer exist. 

396 Views
aaroncouran
Contributor III

The screenshots are both hilarious and inspiring.  I look forward to your blog!

0 Likes
396 Views
mellerbeck
Contributor II

Yes, yes, and more yes! I think what I miss most about Qlikview is there is no Qlikview 'Bible'. I want a book! I would love a book that would take a simple corporation as an example and implement a bunch of different Qlikviews as examples. Building off of each other, and then finally presenting an Executive Dashboard.

That, and did I mention I would like more books about qlikview

396 Views
Employee
Employee

Looks like a very promising start Thank you for sharing your stories, insights and technical expertise!

0 Likes
396 Views
Support
Support

I like the "drill"-icon used back in the days. it's so...Windows 3.1

0 Likes
396 Views
skh
Contributor

Fascinating history! Looking forward to the blogs.

Cheers,

Sunil

0 Likes
396 Views

Thank you for all these positive and enthusiastic comments! I will try make the coming blog posts as interesting. Or I should rather say "we", since there are several QlikTechies that also will write on this a little more "technical" blog.

Cheers

HIC

0 Likes
396 Views
Not applicable

I fully agree with mellerbeck

Books,books and more books......YES PLEASE!!!! These blogs will help a lot. For someone new to Qlikview this is worth gold.

0 Likes
396 Views
aadilmadarveet
Valued Contributor

Just love the little history part... truly amazing... looking forward to more blogs like this...

0 Likes
396 Views
Partner
Partner

Inspiring history... glad to know about those three colors...

0 Likes
396 Views
thirumalaivadiv
New Contributor III

interesting topics..

0 Likes
396 Views
geminihzh
Valued Contributor

Thanks for sharing this kind of small stories from Qlik, like it. I then actually re-read the wiki page for Qlik, and found the word "Quik" stands for "Quality, Understanding, Interaction, Knowledge". 

0 Likes
396 Views

Business card from 1994. Note the Quality - Understanding - Information - Knowledge

Business card QuikTech s.JPG

396 Views
Partner
Partner

And now?
Quality - L... - Information - Knowledge

0 Likes
396 Views

We haven't used this abbreviation for at least 15 years, but this is what my business card looked like in 1996:

Business card QlikTech s.JPG

See also A Historical Odyssey: Quality - Learning - Interaction - Knowledge

396 Views
geminihzh
Valued Contributor

Hi, Heric,

We use Qlik every data, it is a shame that even do not know what it stand for!!!! But get it now. Thanks Henric!!!

0 Likes
396 Views