<?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 Re: SQL SELECT causes problem. in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996933#M650802</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had a similar problem with postal codes. Sometimes and apparently arbitrarily, QlikView loaded the values adding 0's to the left. For example, the value 7500 was sometimes loaded as 07500 and other times as 7500 in records from the same source having the value 7500.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After delving, the issue was related to nonprintable characters, and I solved it by removing all of them in the query, namely replacing CHAR(9), CHAR(13), CHAR(10) and CHAR(163) with the empty string '', as well as applying RTRIM and LTRIM functions to trim the result.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Aug 2015 11:27:27 GMT</pubDate>
    <dc:creator>jldengra</dc:creator>
    <dc:date>2015-08-27T11:27:27Z</dc:date>
    <item>
      <title>SQL SELECT causes problem.</title>
      <link>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996928#M650797</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;My new problem with Qlikview is as following:&lt;/P&gt;&lt;P&gt;I Have table in SQL with column ID that values are:&lt;/P&gt;&lt;P&gt;0 01 02 03 04 05 06 07 08 09 1 10 11 12 13 3 99 (nvchar)&lt;/P&gt;&lt;P&gt;I implement tables with sql select statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I load it in QV I see this table but its column has values:&lt;/P&gt;&lt;P&gt;0 01 02 03 04 05 06 07 08 09 10 11 12 13 99&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So that QV adds '0' to single numbers even numer format is nvchar... It completely ruins my hierarchy tree. How to solve it without creating new table or using update statement (I have no access)&lt;/P&gt;&lt;P&gt;counting on you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Aug 2015 08:53:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996928#M650797</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-08-26T08:53:39Z</dc:date>
    </item>
    <item>
      <title>Re: SQL SELECT couses problem.</title>
      <link>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996929#M650798</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;QlikView didn't care about such special data-types - there are only numeric or string respectively the combination of both as dual-field. But this isn't a problem rather the opposite. You could solve it with converting/formating with functions like num(num#(Field, 'Format'), 'Format') your data within a : &lt;A href="https://community.qlik.com/qlik-blogpost/2972"&gt;Preceding Load&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Aug 2015 09:10:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996929#M650798</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2015-08-26T09:10:49Z</dc:date>
    </item>
    <item>
      <title>Re: SQL SELECT couses problem.</title>
      <link>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996930#M650799</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;try Num(ID) as ID in your script&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Aug 2015 09:17:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996930#M650799</guid>
      <dc:creator>sasiparupudi1</dc:creator>
      <dc:date>2015-08-26T09:17:16Z</dc:date>
    </item>
    <item>
      <title>Re: SQL SELECT couses problem.</title>
      <link>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996931#M650800</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you want ID to be interpreted as a text field, transform it in a preceding load to the SQL:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOAD Text(ID) As ID, Field, Field2...;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SQL SELECT&lt;/P&gt;&lt;P&gt;ID, &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Field, Field2...&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Aug 2015 09:38:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996931#M650800</guid>
      <dc:creator>Ralf-Narfeldt</dc:creator>
      <dc:date>2015-08-26T09:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: SQL SELECT couses problem.</title>
      <link>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996932#M650801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And this is the answer.&lt;/P&gt;&lt;P&gt;Thank you all very much&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Aug 2015 10:29:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996932#M650801</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-08-26T10:29:11Z</dc:date>
    </item>
    <item>
      <title>Re: SQL SELECT causes problem.</title>
      <link>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996933#M650802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had a similar problem with postal codes. Sometimes and apparently arbitrarily, QlikView loaded the values adding 0's to the left. For example, the value 7500 was sometimes loaded as 07500 and other times as 7500 in records from the same source having the value 7500.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After delving, the issue was related to nonprintable characters, and I solved it by removing all of them in the query, namely replacing CHAR(9), CHAR(13), CHAR(10) and CHAR(163) with the empty string '', as well as applying RTRIM and LTRIM functions to trim the result.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Aug 2015 11:27:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996933#M650802</guid>
      <dc:creator>jldengra</dc:creator>
      <dc:date>2015-08-27T11:27:27Z</dc:date>
    </item>
    <item>
      <title>Re: SQL SELECT causes problem.</title>
      <link>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996934#M650803</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;please close this thread by selecting the correct answer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Aug 2015 11:31:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/SQL-SELECT-causes-problem/m-p/996934#M650803</guid>
      <dc:creator>sasiparupudi1</dc:creator>
      <dc:date>2015-08-27T11:31:33Z</dc:date>
    </item>
  </channel>
</rss>

