<?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: 64-bit and 32-bit ODBC issue in Microsoft Integration with SAS</title>
    <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37593#M626</link>
    <description>issue resolved after installing 32-bit and updating the 64-bit version. Yes, I have both versions installed&lt;BR /&gt;
&lt;BR /&gt;
64-Bit: AUTOMATIC SYSVLONG4 9.02.02M0P01152009&lt;BR /&gt;
&lt;BR /&gt;
32-Bit: AUTOMATIC SYSVLONG4 9.02.02M2P09012009&lt;BR /&gt;
&lt;BR /&gt;
My code from the previous post now functions with no errors, so I now can move on with my life.&lt;BR /&gt;
&lt;BR /&gt;
good luck</description>
    <pubDate>Thu, 26 Aug 2010 14:43:51 GMT</pubDate>
    <dc:creator>UMAnalyst</dc:creator>
    <dc:date>2010-08-26T14:43:51Z</dc:date>
    <item>
      <title>64-bit and 32-bit ODBC issue</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37588#M621</link>
      <description>I am working on a 64-bit machine with 32-bit Microsoft office and 32-bit odbc drivers. I used 32-bit version of ODBC Data Source Administrator to create by DSN to connect to a local copy of Microsoft Access database. When I run following code, I get an error:&lt;BR /&gt;
&lt;BR /&gt;
libname msaccess odbc dsn=myDSN;&lt;BR /&gt;
&lt;BR /&gt;
ERROR: CLI error trying to establish connection: [Microsoft][ODBC Driver Manager] Data source&lt;BR /&gt;
       name not found and no default driver specified&lt;BR /&gt;
ERROR: Error in the LIBNAME statement.&lt;BR /&gt;
&lt;BR /&gt;
Is there a way I can specify in libname that i want to use 32-bit odbc? We also don't have Microsoft Access PC/File access to use proc import. I will really appreciate any feedback.</description>
      <pubDate>Fri, 18 Jun 2010 14:05:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37588#M621</guid>
      <dc:creator>model_coder</dc:creator>
      <dc:date>2010-06-18T14:05:17Z</dc:date>
    </item>
    <item>
      <title>Re: 64-bit and 32-bit ODBC issue</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37589#M622</link>
      <description>I'm not sure if "MS Access PC/File access" which you referred to is the same as the SAS PC Files Server. If it isn't and you do have SAS PC Files Server installed, perhaps this will help.&lt;BR /&gt;
&lt;BR /&gt;
back-info: I was recently upgraded to Win 64-bit and had success connecting to 32-bit MS Access DBs (.mdb) by:&lt;BR /&gt;
&lt;BR /&gt;
1)  Starting the SAS PC Files Server, and &lt;BR /&gt;
&lt;BR /&gt;
2) using the LIB statement:&lt;BR /&gt;
    libname &lt;LIBREF&gt; pcfiles server=&lt;SERVER name=""&gt; port=&lt;NUMBER&gt; path=full file path\dbname.mdb&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
To disassociate the reference use: libname &lt;LIBREF&gt; CLEAR;&lt;BR /&gt;
&lt;BR /&gt;
If this helped and you want to return the favor, please tell me how to make this (or some other method) work for 32-bit MS Access 2007 DBs with .accdb extension.&lt;BR /&gt;
&lt;BR /&gt;
To this point, I have found comfort in declaring it impossible.&lt;BR /&gt;
&lt;BR /&gt;
Good Luck&lt;BR /&gt;
&lt;BR /&gt;
Message was edited by: UM Analyst&lt;BR /&gt;
&lt;BR /&gt;
Message was edited by: UM Analyst&lt;BR /&gt;
&lt;BR /&gt;
Message was edited by: UM Analyst&lt;/LIBREF&gt;&lt;/NUMBER&gt;&lt;/SERVER&gt;&lt;/LIBREF&gt;</description>
      <pubDate>Mon, 26 Jul 2010 14:46:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37589#M622</guid>
      <dc:creator>UMAnalyst</dc:creator>
      <dc:date>2010-07-26T14:46:34Z</dc:date>
    </item>
    <item>
      <title>Re: 64-bit and 32-bit ODBC issue</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37590#M623</link>
      <description>We are having the same issue.  We have SAS 64-Bit installed on a Win2k8R2 x64 machine.  When trying to import data from any MS file (Excel, Access, etc) there is the "ERROR: CLI error trying to establish connection: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified" issue.&lt;BR /&gt;
&lt;BR /&gt;
Here's what I found out.&lt;BR /&gt;
&lt;BR /&gt;
It looks like SAS polls the default ODBC driver locations, which is fine for an x86 environment.  However, in an x64 environment, the default location is for the x64 drivers in which MS hasn't released 64 bit ODBC drivers for their office programs.&lt;BR /&gt;
&lt;BR /&gt;
The x86 ODBC drivers do exist and are located on the server.  I need to run the x86 ODBC manager to find and see them, but they are there.  How can I change SAS to poll an alternative or multiple locations when opening an ODBC stream?&lt;BR /&gt;
&lt;BR /&gt;
EDIT: We do NOT have SAS PC Files Server installed.

Message was edited by: JimmyITCS</description>
      <pubDate>Tue, 24 Aug 2010 16:29:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37590#M623</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2010-08-24T16:29:06Z</dc:date>
    </item>
    <item>
      <title>Re: 64-bit and 32-bit ODBC issue</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37591#M624</link>
      <description>See this usage note:&lt;BR /&gt;
&lt;A href="http://support.sas.com/kb/38/779.html" target="_blank"&gt;http://support.sas.com/kb/38/779.html&lt;/A&gt;</description>
      <pubDate>Tue, 24 Aug 2010 19:17:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37591#M624</guid>
      <dc:creator>CaseySmith</dc:creator>
      <dc:date>2010-08-24T19:17:03Z</dc:date>
    </item>
    <item>
      <title>Re: 64-bit and 32-bit ODBC issue</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37592#M625</link>
      <description>PERFECT!  Now, why is this information so hard to find?!</description>
      <pubDate>Tue, 24 Aug 2010 19:24:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37592#M625</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2010-08-24T19:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: 64-bit and 32-bit ODBC issue</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37593#M626</link>
      <description>issue resolved after installing 32-bit and updating the 64-bit version. Yes, I have both versions installed&lt;BR /&gt;
&lt;BR /&gt;
64-Bit: AUTOMATIC SYSVLONG4 9.02.02M0P01152009&lt;BR /&gt;
&lt;BR /&gt;
32-Bit: AUTOMATIC SYSVLONG4 9.02.02M2P09012009&lt;BR /&gt;
&lt;BR /&gt;
My code from the previous post now functions with no errors, so I now can move on with my life.&lt;BR /&gt;
&lt;BR /&gt;
good luck</description>
      <pubDate>Thu, 26 Aug 2010 14:43:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37593#M626</guid>
      <dc:creator>UMAnalyst</dc:creator>
      <dc:date>2010-08-26T14:43:51Z</dc:date>
    </item>
    <item>
      <title>Re: 64-bit and 32-bit ODBC issue</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37594#M627</link>
      <description>We have SAS/Access interface to PC files installed on our machines. But I don't see the PC File server component. Do we need a separate license for this component?</description>
      <pubDate>Tue, 30 Nov 2010 01:06:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/64-bit-and-32-bit-ODBC-issue/m-p/37594#M627</guid>
      <dc:creator>model_coder</dc:creator>
      <dc:date>2010-11-30T01:06:34Z</dc:date>
    </item>
  </channel>
</rss>

