<?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: SAS/Access connection to sql server in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/SAS-Access-connection-to-sql-server/m-p/361026#M85093</link>
    <description>I have no idea.&lt;BR /&gt;Ideally this can be replicated from a non-SAS ODBC client.&lt;BR /&gt;Perhaps a ticket to SAS tech support is your best shot.</description>
    <pubDate>Wed, 24 May 2017 06:12:45 GMT</pubDate>
    <dc:creator>LinusH</dc:creator>
    <dc:date>2017-05-24T06:12:45Z</dc:date>
    <item>
      <title>SAS/Access connection to sql server</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Access-connection-to-sql-server/m-p/360953#M85059</link>
      <description>&lt;P&gt;Any ideas on why (or how to turn off) I'm getting a warning message that says a SQL Server job that was submitted started successfully?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;WARNING: During execute: [SAS/ACCESS][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Job &lt;BR /&gt; 'A2A25B47-24FC-498B-B738-E89C3AD1AAB7' started successfully.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm guessing that the warning doesn't mean much...but it is confusing to see it.&lt;/P&gt;</description>
      <pubDate>Tue, 23 May 2017 22:58:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Access-connection-to-sql-server/m-p/360953#M85059</guid>
      <dc:creator>DBailey</dc:creator>
      <dc:date>2017-05-23T22:58:22Z</dc:date>
    </item>
    <item>
      <title>Re: SAS/Access connection to sql server</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Access-connection-to-sql-server/m-p/361026#M85093</link>
      <description>I have no idea.&lt;BR /&gt;Ideally this can be replicated from a non-SAS ODBC client.&lt;BR /&gt;Perhaps a ticket to SAS tech support is your best shot.</description>
      <pubDate>Wed, 24 May 2017 06:12:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Access-connection-to-sql-server/m-p/361026#M85093</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2017-05-24T06:12:45Z</dc:date>
    </item>
  </channel>
</rss>

