<?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 Externalized ODBC Connection String in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Externalized-ODBC-Connection-String/m-p/171219#M41311</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have implemented an external config file that contains client specific ODBC connection strings for the data loads.&lt;/P&gt;&lt;P&gt;Utilizing the QVScrambler.dll I can programatically scramble the username and password and store these values.&lt;/P&gt;&lt;P&gt;My fear is that someday QVScramler.dll might go away, and I'll be left with unscrambled data (short of keeping a local version of the dll and distributing it).&lt;/P&gt;&lt;P&gt;My question is: Is the code that scrambles/unscrambles just some .net method? or is it some proprietary QV routine?&lt;/P&gt;&lt;P&gt;I find it strange that externalizing the connection string isn't a commonly requested feature, eliminating the need to open up a qvw and modify it during deployment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Dec 2009 23:03:22 GMT</pubDate>
    <dc:creator />
    <dc:date>2009-12-01T23:03:22Z</dc:date>
    <item>
      <title>Externalized ODBC Connection String</title>
      <link>https://community.qlik.com/t5/QlikView/Externalized-ODBC-Connection-String/m-p/171219#M41311</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have implemented an external config file that contains client specific ODBC connection strings for the data loads.&lt;/P&gt;&lt;P&gt;Utilizing the QVScrambler.dll I can programatically scramble the username and password and store these values.&lt;/P&gt;&lt;P&gt;My fear is that someday QVScramler.dll might go away, and I'll be left with unscrambled data (short of keeping a local version of the dll and distributing it).&lt;/P&gt;&lt;P&gt;My question is: Is the code that scrambles/unscrambles just some .net method? or is it some proprietary QV routine?&lt;/P&gt;&lt;P&gt;I find it strange that externalizing the connection string isn't a commonly requested feature, eliminating the need to open up a qvw and modify it during deployment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Dec 2009 23:03:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Externalized-ODBC-Connection-String/m-p/171219#M41311</guid>
      <dc:creator />
      <dc:date>2009-12-01T23:03:22Z</dc:date>
    </item>
  </channel>
</rss>

