Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Access vs. QlikView for building data associations?

I've had a few people tell me they build their associations & keys in  Access database first (data model), and then only bring into QlikView once the data is just right and links & associations are already made.

I don't know anything about Access, and have serveral months of experience using QlikView. In my time, I have not found any reason to move my data from Excel files into Access first. I find through scripting in QlikView I am able to aheive what I need. I trust those who told me that, they are pretty tech savy. However, I wanted to get feedback from this community and those experienced with Access.

Is there any advantage to building queries first in Access and then moving the data to QlikView, or do you prefer to do all your data modeling in the QlikView Script?

If helpful, the original source files are monthly results that are available first in Excel (CSV) files.

1 Reply
Not applicable
Author

There is no advantage as you will need to create Keys in Access to link the tables and build the data model. As you know QlikView is working a little bit different and you have to adjust the data model when loading. So I can't see any reason to do it first in Access.