<?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: Proc Import Access Table stored on PC (C:\ drive) in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Proc-Import-Access-Table-stored-on-PC-C-drive/m-p/5053#M1609</link>
    <description>I may have missed a point here Doc, but the writer says the file is on his local drive, and imports correctly using SAS locally.  This seems to be expected results.&lt;BR /&gt;
&lt;BR /&gt;
However, using E.G. on his Unix server, it fails.  The difference is that the engine is on Unix and not on his local machine, so getting to the file becomes a problem.&lt;BR /&gt;
&lt;BR /&gt;
Unix reading Windows will need something like Samba to map the environment.&lt;BR /&gt;
&lt;BR /&gt;
Then the users C drive needs to be shared.&lt;BR /&gt;
&lt;BR /&gt;
Then Unix needs a path that may be fairly obscure to point to the machine and the share name and pick up the file.&lt;BR /&gt;
&lt;BR /&gt;
Finally, the Unix server needs to have a license to import PC File Format files, which may also be an issue.&lt;BR /&gt;
&lt;BR /&gt;
There may be too many hurdles on this steeplechase for anyone but Tech Support to cross.&lt;BR /&gt;
&lt;BR /&gt;
Kind regards&lt;BR /&gt;
&lt;BR /&gt;
David</description>
    <pubDate>Mon, 15 Oct 2007 08:51:40 GMT</pubDate>
    <dc:creator>deleted_user</dc:creator>
    <dc:date>2007-10-15T08:51:40Z</dc:date>
    <item>
      <title>Proc Import Access Table stored on PC (C:\ drive)</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Proc-Import-Access-Table-stored-on-PC-C-drive/m-p/5051#M1607</link>
      <description>Is it possible to use the Proc Import statement in SAS EG Guide 4 when the database I am trying to import is stored locally on my PC?  It is on my "C:" drive.  When I use SAS 9.1 (PC Sas) I am import my database with a Proc Import but i keep getting an error message when using EG Guide 4.  Is it possible to import from your local PC while running EG Guide on the Unix Server?&lt;BR /&gt;
&lt;BR /&gt;
Any help would be greatly appreciated, I am fairly new to SAS.</description>
      <pubDate>Fri, 12 Oct 2007 13:06:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Proc-Import-Access-Table-stored-on-PC-C-drive/m-p/5051#M1607</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2007-10-12T13:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Import Access Table stored on PC (C:\ drive)</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Proc-Import-Access-Table-stored-on-PC-C-drive/m-p/5052#M1608</link>
      <description>VtNick,&lt;BR /&gt;
&lt;BR /&gt;
It should be possible, it certainly is a choice on the Import menus.  Without knowing the message it's hard for us on the forum to help.  Your best bets on resolving an error message are &lt;BR /&gt;
&lt;BR /&gt;
1) go to support.sas.com and put a "significant" part of the message into the search field (put quotes around it so it searches for the phrase).  I usually get a useful answer on the first page that way.&lt;BR /&gt;
2) call technical support.&lt;BR /&gt;
&lt;BR /&gt;
On the Unix server, EGuide runs on the Windows XP as a client (only), and you can have SAS 9.1.3 running on Unix as a server.  You may need to use a libname statement to get to the Access DB (see the SAS/Access to PC file formats documentation for that part).&lt;BR /&gt;
&lt;BR /&gt;
Doc Muhlbaier</description>
      <pubDate>Sun, 14 Oct 2007 19:17:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Proc-Import-Access-Table-stored-on-PC-C-drive/m-p/5052#M1608</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2007-10-14T19:17:51Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Import Access Table stored on PC (C:\ drive)</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Proc-Import-Access-Table-stored-on-PC-C-drive/m-p/5053#M1609</link>
      <description>I may have missed a point here Doc, but the writer says the file is on his local drive, and imports correctly using SAS locally.  This seems to be expected results.&lt;BR /&gt;
&lt;BR /&gt;
However, using E.G. on his Unix server, it fails.  The difference is that the engine is on Unix and not on his local machine, so getting to the file becomes a problem.&lt;BR /&gt;
&lt;BR /&gt;
Unix reading Windows will need something like Samba to map the environment.&lt;BR /&gt;
&lt;BR /&gt;
Then the users C drive needs to be shared.&lt;BR /&gt;
&lt;BR /&gt;
Then Unix needs a path that may be fairly obscure to point to the machine and the share name and pick up the file.&lt;BR /&gt;
&lt;BR /&gt;
Finally, the Unix server needs to have a license to import PC File Format files, which may also be an issue.&lt;BR /&gt;
&lt;BR /&gt;
There may be too many hurdles on this steeplechase for anyone but Tech Support to cross.&lt;BR /&gt;
&lt;BR /&gt;
Kind regards&lt;BR /&gt;
&lt;BR /&gt;
David</description>
      <pubDate>Mon, 15 Oct 2007 08:51:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Proc-Import-Access-Table-stored-on-PC-C-drive/m-p/5053#M1609</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2007-10-15T08:51:40Z</dc:date>
    </item>
  </channel>
</rss>

