<?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 Import Data versus Open Data in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Import-Data-versus-Open-Data/m-p/5452#M1735</link>
    <description>Is there any difference whether I use File&amp;gt;Import Data and File&amp;gt;Open&amp;gt;Data from a the same Excel file?</description>
    <pubDate>Mon, 12 Nov 2007 08:40:25 GMT</pubDate>
    <dc:creator>deleted_user</dc:creator>
    <dc:date>2007-11-12T08:40:25Z</dc:date>
    <item>
      <title>Import Data versus Open Data</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Import-Data-versus-Open-Data/m-p/5452#M1735</link>
      <description>Is there any difference whether I use File&amp;gt;Import Data and File&amp;gt;Open&amp;gt;Data from a the same Excel file?</description>
      <pubDate>Mon, 12 Nov 2007 08:40:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Import-Data-versus-Open-Data/m-p/5452#M1735</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2007-11-12T08:40:25Z</dc:date>
    </item>
    <item>
      <title>Re: Import Data versus Open Data</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Import-Data-versus-Open-Data/m-p/5453#M1736</link>
      <description>yes.&lt;BR /&gt;
&lt;BR /&gt;
Import data (and the create a SAS dataset option under File&amp;gt;Open&amp;gt;data) create a SAS dataset from the excel sheet.  To re-import, you have to re-run the task.&lt;BR /&gt;
&lt;BR /&gt;
file&amp;gt;open&amp;gt;data also allows you to open the excel file "in place" so changes to the excel file appear immediately to the project.&lt;BR /&gt;
&lt;BR /&gt;
IMHO, import data allows a little more flexibility at the expense of immediacy.&lt;BR /&gt;
&lt;BR /&gt;
Doc Muhlbaier</description>
      <pubDate>Mon, 12 Nov 2007 17:52:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Import-Data-versus-Open-Data/m-p/5453#M1736</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2007-11-12T17:52:56Z</dc:date>
    </item>
    <item>
      <title>Re: Import Data versus Open Data</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Import-Data-versus-Open-Data/m-p/5454#M1737</link>
      <description>I agree, and I have a number of memories of batches and projects failing because one piece of software locked something required by another.&lt;BR /&gt;
&lt;BR /&gt;
Excel was a particular issue, but then often the Excel objects were not created for the SAS process but used as an input.  It would be unkind to blame Excel for blocking something it wasn't designed to do.&lt;BR /&gt;
&lt;BR /&gt;
Import will allow the data to be taken (and the import to be bypassed in some project updates if required), whereas Open will require that a file lock can be obtained every time the project is opened.&lt;BR /&gt;
&lt;BR /&gt;
Kind regards&lt;BR /&gt;
&lt;BR /&gt;
David</description>
      <pubDate>Wed, 14 Nov 2007 02:11:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Import-Data-versus-Open-Data/m-p/5454#M1737</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2007-11-14T02:11:45Z</dc:date>
    </item>
  </channel>
</rss>

