<?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 How to read data beyond ASCII(0) from ADO/MSDASQL in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/How-to-read-data-beyond-ASCII-0-from-ADO-MSDASQL/m-p/208945#M715476</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;some additional information: the field is defined as a fixed length string (char(320)) database type. as I understood from articles on the net, the ADO/MSDASQL engine normally expects char(0) as the EOS character. However, when copying the table through DTS to a SQL Server 2000 database, ALL data in the field (including the null char) gets copied. So there must be a setting in the driver/receiving engine that capacitates that, I just haven't found it yet.........&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Jan 2010 09:58:19 GMT</pubDate>
    <dc:creator>happydays1967</dc:creator>
    <dc:date>2010-01-15T09:58:19Z</dc:date>
    <item>
      <title>How to read data beyond ASCII(0) from ADO/MSDASQL</title>
      <link>https://community.qlik.com/t5/QlikView/How-to-read-data-beyond-ASCII-0-from-ADO-MSDASQL/m-p/208944#M715475</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Hope that someone can help me on this one: I am reading data from a database using either ODBC or OLE DB connection. In the record, I have one field that contains a string of characters, of which some, or all are the ascii 0 character (chr(0)), which is usually the end of string character for this type of connection. Hence, only data up to the ascii 0 character is read, the rest is discarded. Does anybody know how to circumvent this, and load all data from this field, including the ascii 0 characters? All help is welcome!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Jan 2010 17:15:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/How-to-read-data-beyond-ASCII-0-from-ADO-MSDASQL/m-p/208944#M715475</guid>
      <dc:creator>happydays1967</dc:creator>
      <dc:date>2010-01-12T17:15:16Z</dc:date>
    </item>
    <item>
      <title>How to read data beyond ASCII(0) from ADO/MSDASQL</title>
      <link>https://community.qlik.com/t5/QlikView/How-to-read-data-beyond-ASCII-0-from-ADO-MSDASQL/m-p/208945#M715476</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;some additional information: the field is defined as a fixed length string (char(320)) database type. as I understood from articles on the net, the ADO/MSDASQL engine normally expects char(0) as the EOS character. However, when copying the table through DTS to a SQL Server 2000 database, ALL data in the field (including the null char) gets copied. So there must be a setting in the driver/receiving engine that capacitates that, I just haven't found it yet.........&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jan 2010 09:58:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/How-to-read-data-beyond-ASCII-0-from-ADO-MSDASQL/m-p/208945#M715476</guid>
      <dc:creator>happydays1967</dc:creator>
      <dc:date>2010-01-15T09:58:19Z</dc:date>
    </item>
  </channel>
</rss>

