<?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: Restricting Excel data with DB2 data in Microsoft Integration with SAS</title>
    <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Restricting-Excel-data-with-DB2-data/m-p/67082#M911</link>
    <description>Complicated, yes. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; &lt;BR /&gt;
There is a Pivot-table from where the user is selecting some data. When (s)he has selected the data (s)he would like to compare one column of the selection with DB2 table to see which sells are not in the DB2 table. &lt;BR /&gt;
&lt;BR /&gt;
The DB2 table could have more than 65 000 rows, so I can't just 'bring it over' from mainframe. So I should be able to get the selected data from the excel table and transfer it to mainframe and exclude the data that is in DB2 and show the 'leftovers' on the excel sheet.</description>
    <pubDate>Thu, 27 Aug 2009 07:23:34 GMT</pubDate>
    <dc:creator>Virpi</dc:creator>
    <dc:date>2009-08-27T07:23:34Z</dc:date>
    <item>
      <title>Restricting Excel data with DB2 data</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Restricting-Excel-data-with-DB2-data/m-p/67080#M909</link>
      <description>Is there a way for restricting rows on excel sheet by selecting those who are not present in DB2 table? &lt;BR /&gt;
AMO Analyze Data / Compare is not giving the answer easily and the result is not what is wanted. &lt;BR /&gt;
&lt;BR /&gt;
Can we capsule selected area on excel sheet and call stored process and use the capsulated data as parameter?</description>
      <pubDate>Wed, 26 Aug 2009 12:20:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Restricting-Excel-data-with-DB2-data/m-p/67080#M909</guid>
      <dc:creator>Virpi</dc:creator>
      <dc:date>2009-08-26T12:20:17Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting Excel data with DB2 data</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Restricting-Excel-data-with-DB2-data/m-p/67081#M910</link>
      <description>Please tell us more about this application.&lt;BR /&gt;
From this brief information, I think this sounds a bit complicated. If you could the "original" data stored in DB2/SAS, you could create a view or a result set that could be displayed in AMO/Excel...?&lt;BR /&gt;
&lt;BR /&gt;
/Linus</description>
      <pubDate>Thu, 27 Aug 2009 06:55:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Restricting-Excel-data-with-DB2-data/m-p/67081#M910</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2009-08-27T06:55:53Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting Excel data with DB2 data</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Restricting-Excel-data-with-DB2-data/m-p/67082#M911</link>
      <description>Complicated, yes. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; &lt;BR /&gt;
There is a Pivot-table from where the user is selecting some data. When (s)he has selected the data (s)he would like to compare one column of the selection with DB2 table to see which sells are not in the DB2 table. &lt;BR /&gt;
&lt;BR /&gt;
The DB2 table could have more than 65 000 rows, so I can't just 'bring it over' from mainframe. So I should be able to get the selected data from the excel table and transfer it to mainframe and exclude the data that is in DB2 and show the 'leftovers' on the excel sheet.</description>
      <pubDate>Thu, 27 Aug 2009 07:23:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Restricting-Excel-data-with-DB2-data/m-p/67082#M911</guid>
      <dc:creator>Virpi</dc:creator>
      <dc:date>2009-08-27T07:23:34Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting Excel data with DB2 data</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Restricting-Excel-data-with-DB2-data/m-p/67083#M912</link>
      <description>Now I understand better your current situation, but not why. This look-up to DB2 seems like an data quality check-up? If so, I don't think this not best solved by some end-user application. I would prefer some data preparation where you could match your sales data on beforehand and present the complete result to the user (in a pivot).&lt;BR /&gt;
/Linus</description>
      <pubDate>Thu, 27 Aug 2009 13:51:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Restricting-Excel-data-with-DB2-data/m-p/67083#M912</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2009-08-27T13:51:50Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting Excel data with DB2 data</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Restricting-Excel-data-with-DB2-data/m-p/67084#M913</link>
      <description>You can use Copy To SAS Server (in the Active Data dropdown or menu in toolbar/ribbon) to save the selected Excel data as a SAS data set to your server, then run whatever comparison code you would like on the server.</description>
      <pubDate>Thu, 27 Aug 2009 14:00:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/Restricting-Excel-data-with-DB2-data/m-p/67084#M913</guid>
      <dc:creator>CaseySmith</dc:creator>
      <dc:date>2009-08-27T14:00:46Z</dc:date>
    </item>
  </channel>
</rss>

