<?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: Pull date range with datetime20. in ODS and Base Reporting</title>
    <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Pull-date-range-with-datetime20/m-p/529374#M22241</link>
    <description>&lt;P&gt;Oracle (and any other DBMS I know of) does not have the concept of macro variables. If you use explicit pass-through, you have to convert the code to Oracle standards first, and have macro variables resolved to Oracle-compatible formats.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Jan 2019 11:44:32 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2019-01-23T11:44:32Z</dc:date>
    <item>
      <title>Pull date range with datetime20.</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Pull-date-range-with-datetime20/m-p/529280#M22238</link>
      <description>I have a macro that should filter start and end date ..it suppose to bring yesterday but it brings everything its an oracle platform&lt;BR /&gt;&lt;BR /&gt;Data _null_;&lt;BR /&gt;Format c date7. E date7.;&lt;BR /&gt;C=datepart (datetime()));&lt;BR /&gt;E=c-1;&lt;BR /&gt;Call symput ('cdate2', "'"||vvalue(e)||"'d'");&lt;BR /&gt;Run;&lt;BR /&gt;&lt;BR /&gt;%put &amp;amp;cdate2.;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Where datepart (created)&amp;gt;&amp;amp;cdate2&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 22 Jan 2019 21:58:01 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Pull-date-range-with-datetime20/m-p/529280#M22238</guid>
      <dc:creator>Gil_</dc:creator>
      <dc:date>2019-01-22T21:58:01Z</dc:date>
    </item>
    <item>
      <title>Re: Pull date range with datetime20.</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Pull-date-range-with-datetime20/m-p/529288#M22239</link>
      <description>&lt;P&gt;Are you sure that the Oracle side will understand a SAS MACRO variable of form '21JAN19'd?&lt;/P&gt;
&lt;P&gt;I don't use Oracle but have seen a number of questions here about passing macro values to Oracle that make me believe this may not be appropriate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It would likely help those who know more about Oracle than I do to include your connection info and the code using this macro variable. XXXX out anything like user or password in the connection.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jan 2019 22:14:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Pull-date-range-with-datetime20/m-p/529288#M22239</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2019-01-22T22:14:23Z</dc:date>
    </item>
    <item>
      <title>Re: Pull date range with datetime20.</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Pull-date-range-with-datetime20/m-p/529374#M22241</link>
      <description>&lt;P&gt;Oracle (and any other DBMS I know of) does not have the concept of macro variables. If you use explicit pass-through, you have to convert the code to Oracle standards first, and have macro variables resolved to Oracle-compatible formats.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jan 2019 11:44:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Pull-date-range-with-datetime20/m-p/529374#M22241</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2019-01-23T11:44:32Z</dc:date>
    </item>
  </channel>
</rss>

