<?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 Excel import: forcing column to be numeric in absence of MIXED in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Excel-import-forcing-column-to-be-numeric-in-absence-of-MIXED/m-p/486339#M71929</link>
    <description>&lt;P&gt;Dear community,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am having issues importing some excel files using EXCELCS or XLSX engines (only ones available due to bitness differences): as neither XLSX engine nor EXCELCS support MIXED option, if there are any (XLSX) resp. sufficient text values in the first rows (EXCELCS), the entire column gets imported as text. With XLSX engine this additionally leads to dates being saved as internal excel timestamps - number of days since 1 January 1900.&lt;/P&gt;&lt;P&gt;I tried using&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;dbdsopts="dbsastype=(var_mixed=NUMERIC)"&lt;/PRE&gt;&lt;P&gt;with EXCELCS engine but this does not work - I am getting the following error:&lt;/P&gt;&lt;P&gt;ERROR: During read: [Microsoft][ODBC-Treiber für Excel]Ungültiger Zeichenwert für Konvertierungsangabe. bei Spaltennummer 3 (var_mixed)&lt;/P&gt;&lt;P&gt;It appears that dbsastype option can force the numeric values to be imported as text but not the other way round. Is this a known limitation? Are there any other options?&amp;nbsp;Unfortunately getting the file as .csv is not possible. Thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 13 Aug 2018 12:54:16 GMT</pubDate>
    <dc:creator>js5</dc:creator>
    <dc:date>2018-08-13T12:54:16Z</dc:date>
    <item>
      <title>Excel import: forcing column to be numeric in absence of MIXED</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Excel-import-forcing-column-to-be-numeric-in-absence-of-MIXED/m-p/486339#M71929</link>
      <description>&lt;P&gt;Dear community,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am having issues importing some excel files using EXCELCS or XLSX engines (only ones available due to bitness differences): as neither XLSX engine nor EXCELCS support MIXED option, if there are any (XLSX) resp. sufficient text values in the first rows (EXCELCS), the entire column gets imported as text. With XLSX engine this additionally leads to dates being saved as internal excel timestamps - number of days since 1 January 1900.&lt;/P&gt;&lt;P&gt;I tried using&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;dbdsopts="dbsastype=(var_mixed=NUMERIC)"&lt;/PRE&gt;&lt;P&gt;with EXCELCS engine but this does not work - I am getting the following error:&lt;/P&gt;&lt;P&gt;ERROR: During read: [Microsoft][ODBC-Treiber für Excel]Ungültiger Zeichenwert für Konvertierungsangabe. bei Spaltennummer 3 (var_mixed)&lt;/P&gt;&lt;P&gt;It appears that dbsastype option can force the numeric values to be imported as text but not the other way round. Is this a known limitation? Are there any other options?&amp;nbsp;Unfortunately getting the file as .csv is not possible. Thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 12:54:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Excel-import-forcing-column-to-be-numeric-in-absence-of-MIXED/m-p/486339#M71929</guid>
      <dc:creator>js5</dc:creator>
      <dc:date>2018-08-13T12:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: Excel import: forcing column to be numeric in absence of MIXED</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Excel-import-forcing-column-to-be-numeric-in-absence-of-MIXED/m-p/486343#M71930</link>
      <description>&lt;P&gt;Excel is a really bad format for data.&amp;nbsp; Proc import is a really bad way to read data into SAS (as its a guessing procedure).&amp;nbsp; Add the two together and what you have is GIGO (Garbage In, Garbage Out).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Get the data in a usable format like CSV which is open, plain text, cross platform/bitness.&lt;/P&gt;
&lt;P&gt;Write a datastep program to correctly read in the CSV file, setting lengths, informats, etc. as you know the data should be (presumably from your data import agreement).&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 13:26:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Excel-import-forcing-column-to-be-numeric-in-absence-of-MIXED/m-p/486343#M71930</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2018-08-13T13:26:59Z</dc:date>
    </item>
    <item>
      <title>Re: Excel import: forcing column to be numeric in absence of MIXED</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Excel-import-forcing-column-to-be-numeric-in-absence-of-MIXED/m-p/486354#M71931</link>
      <description>&lt;P&gt;It's totally easy to get a csv from the Excel crap. Open in a spreadsheet program of your choice (I recommend OpenOffice or LibreOffice) and save as csv. With proper software, this action can even be scripted from the commandline.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 14:22:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Excel-import-forcing-column-to-be-numeric-in-absence-of-MIXED/m-p/486354#M71931</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-08-13T14:22:03Z</dc:date>
    </item>
  </channel>
</rss>

