<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic QlikView vs. Access for Linking Excel files &amp; data model in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/QlikView-vs-Access-for-Linking-Excel-files-data-model/m-p/736986#M674805</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've had a few people tell me they build their associations &amp;amp; keys in&amp;nbsp; Access database first (data model), and then only bring into QlikView once the data is just right and links &amp;amp; associations are already made. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If helpful, the original source files are monthly results that are available first in Excel (CSV) files.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 Jul 2014 04:53:06 GMT</pubDate>
    <dc:creator />
    <dc:date>2014-07-24T04:53:06Z</dc:date>
    <item>
      <title>QlikView vs. Access for Linking Excel files &amp; data model</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-vs-Access-for-Linking-Excel-files-data-model/m-p/736986#M674805</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've had a few people tell me they build their associations &amp;amp; keys in&amp;nbsp; Access database first (data model), and then only bring into QlikView once the data is just right and links &amp;amp; associations are already made. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If helpful, the original source files are monthly results that are available first in Excel (CSV) files.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jul 2014 04:53:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-vs-Access-for-Linking-Excel-files-data-model/m-p/736986#M674805</guid>
      <dc:creator />
      <dc:date>2014-07-24T04:53:06Z</dc:date>
    </item>
  </channel>
</rss>

