<?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: link  two tables - not exact match in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175664#M33732</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a rule that describes that 1111BO could be matched with 111150?&lt;/P&gt;&lt;P&gt;Besides that, I would build a format from the NAICS table, with an OTHER value which you could test on.&lt;/P&gt;&lt;P&gt;So, in the data step, first put for an exact match, if it's not a hit, put with a substr() on I-O code (4 pos, then might even 3 pos if there are still misss matches.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Dec 2013 21:50:57 GMT</pubDate>
    <dc:creator>LinusH</dc:creator>
    <dc:date>2013-12-17T21:50:57Z</dc:date>
    <item>
      <title>link  two tables - not exact match</title>
      <link>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175663#M33731</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Forum Members,&lt;/P&gt;&lt;P&gt;Thanks for taking time to read my request !!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Attached are two tables I want to link.&lt;/P&gt;&lt;OL style="list-style-type: decimal;"&gt;&lt;LI&gt;I-O table contains three types of variables: (1) I-O industry,&amp;nbsp; (2) industry name (3) 1997 NAICS code&lt;/LI&gt;&lt;LI&gt;NAICS97 table contains 1&amp;nbsp; variable only : NAICS &lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;OL style="list-style-type: decimal;"&gt;&lt;LI&gt;My objective is to match I-O industry with NAICS in NAICS97 table &lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL style="list-style-type: lower-alpha;"&gt;&lt;LI&gt;e.g. I-O code 1111B0 corresponds to 11115, and in NAICS97 table, we have 111150 , so I would consider that a match, i.e. 1111B0 matches with 111150&lt;/LI&gt;&lt;/OL&gt;&lt;P style="margin-left: .25in;"&gt;I can see that the exact match may lead to very sparse matches. So the alternative is to use I-O industry at 4 digit level. E.g. I-O industry 1110 contains 10 different detailed I-O code, a coarse match would consider any of the following NAICS goes to 1110 industry and its sub-industry.&lt;/P&gt;&lt;TABLE border="0" cellpadding="0" cellspacing="0" style="margin-left: 4.65pt;" width="439"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="73"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11111&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="67"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11112&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="73"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11113&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="67"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11114&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="65"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11115&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="47"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11116&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="47"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11119&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="73"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;1112&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="73"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11131&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="67"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11132&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="65"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;111331 &lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="47"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;111332&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="47"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;111333&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="47"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;111334&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="47"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;111336&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="47"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;111339&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="73"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;111335&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="73"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;1114&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="73"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11191&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="73"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11192&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="73"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11193&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="67"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;111991&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="73"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;11194&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="67"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;111992&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD nowrap="nowrap" style="padding: 0 5.4pt 0 5.4pt;" valign="bottom" width="65"&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10.0pt; font-family: 'Arial','sans-serif';"&gt;111998&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ideally I would like to first do an exact match, then see if I lose many observations, I will do the coarse match. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could someone gives a sample code to do this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Dec 2013 19:10:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175663#M33731</guid>
      <dc:creator>LanMin</dc:creator>
      <dc:date>2013-12-17T19:10:55Z</dc:date>
    </item>
    <item>
      <title>Re: link  two tables - not exact match</title>
      <link>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175664#M33732</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a rule that describes that 1111BO could be matched with 111150?&lt;/P&gt;&lt;P&gt;Besides that, I would build a format from the NAICS table, with an OTHER value which you could test on.&lt;/P&gt;&lt;P&gt;So, in the data step, first put for an exact match, if it's not a hit, put with a substr() on I-O code (4 pos, then might even 3 pos if there are still misss matches.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Dec 2013 21:50:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175664#M33732</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2013-12-17T21:50:57Z</dc:date>
    </item>
    <item>
      <title>Re: link  two tables - not exact match</title>
      <link>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175665#M33733</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, LinusH. I-O tables shows that on row 1111BO, it corresponds to 111113, 111114, 11115, 11116, 111119, I use 111150 as a match to right censor the zero. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what do you mean by 3 pos?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Dec 2013 22:39:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175665#M33733</guid>
      <dc:creator>LanMin</dc:creator>
      <dc:date>2013-12-17T22:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: link  two tables - not exact match</title>
      <link>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175666#M33734</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; The matching keys to NAICS already seem to exist in the I-O table. The exception seems to be at the I-O sector (no I-O code) and subsector level (4 digit I-O codes). But . . .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Setting the exceptions aside for now . . . .In your I-O table, all I-O codes below the sector and subsector level have one-to-many columns of matching NAICS codes. Note the NAICS codes in your I-O table are not necessarily at the lowest level of classification. (NAICS is broken down by sectors (2-digit), subsector (3-digit), industry groups (4-digit), industries (5-digit) and "national industries" (6-digit)). Each NAICS "code" in your I-O table can be matched to the corresponding NAICS codes, at the appropriate level of detail, in a table having a complete listing of NAICS codes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But, your NAICS97 table does not have a complete enumeration of all NAICS codes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, I-O industry 115000 (Agriculture and forestry support activities) shows that NAICS subsector 115 (Support Activities for Agriculture and Forestry) is related. (This implies that all 6-digit codes in NAICS subsector 115 are related to I-O industry 115000). But your NAICS97 table has &lt;STRONG&gt;no&lt;/STRONG&gt; entries starting with 115.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Is NAICS97 deliberately incomplete (missing sector, subsector, industry group, industry or national industry)??&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;In any case, I do not think you can use the I-O code alone to match to NAICS, except very crudely at the 4-digit level. (Results would be inaccurate in many cases). You need to use the NAICS codes on your I-O table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Dec 2013 00:16:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175666#M33734</guid>
      <dc:creator>Fugue</dc:creator>
      <dc:date>2013-12-18T00:16:39Z</dc:date>
    </item>
    <item>
      <title>Re: link  two tables - not exact match</title>
      <link>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175667#M33735</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you, Fugue!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;my previous attached file NAICS97 contains only fiscal year 1997 data (at least according to the database I extract it from). Attached is a more complete NAICS list, it contains 115 as you suggested in your example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I agree the exact match is not ideal. My understandings is I-O industry classification by Bureau of Economic Analysis has more detailed industry classifications than NAICS and SIC ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;suppose I want to match at 4 digit I-O industry level, how should I code this,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;do I have to write many if statement, such as&lt;/P&gt;&lt;P&gt;i-o industry animal production 1130:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if NAICS="1131" OR "1132" OR "1133" THEN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NAICS_all table has the following entries&lt;/P&gt;&lt;P&gt;113&lt;/P&gt;&lt;P&gt;113110&lt;/P&gt;&lt;P&gt;113210&lt;/P&gt;&lt;P&gt;113310&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;which one should I match with which.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Dec 2013 03:06:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175667#M33735</guid>
      <dc:creator>LanMin</dc:creator>
      <dc:date>2013-12-18T03:06:21Z</dc:date>
    </item>
    <item>
      <title>Re: link  two tables - not exact match</title>
      <link>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175668#M33736</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As an aside, I doubt that the I-O codes are more detailed than NAICS: the I-O codes are basically a collapsed version of NAICS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To reiterate my previous point, I don't think you can use the I-O code to match to NAICS codes, except &lt;STRONG&gt;crudely&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, I-O industry 1111A0 Oilseed farming is related to NAICS codes 11111 and 11112 according to your I-O table. Based on this sample, you could assume that the first four digits of the I-O code match the first 4 digits of the NAICS code in the NAICS97 table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But, I-O industry 1111B0 Grain farming also begins with 1111; however, it is related to different NAICS codes (11113, 11114, 11115, 11116, and 11119). Matching between the first four digits of the I-O code and the first four digits in the NAICS97 table in the above two examples would return erroneous matches.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Given that you are trying to match the I-O file and the NAICS97 file for whatever reason, then I suggest that you match the "related 1997 NAICS codes" from the I-O file to the codes in the NAICS97 file. A couple of different ways you could do this:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;split the I-O data so that you have one row for every "related 1997 NAICS code". For example, you could split the row for 1111A0 Oilseed farming into two rows: one for NAICS 11111 and one for 11112. Then you can match NAICS to NAICS.&lt;/LI&gt;&lt;LI&gt;alternatively, read the "related 1997 NAICS codes" in the I-O table into a dataset with separate columns for each related NAICS code. Then, match NAICS97 based on an "IN" comparison to that range of columns.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I strongly suggest you do not use the I-O codes to attempt exact matches to the NAICS table unless you are ok with fuzzy matches.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Dec 2013 22:35:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175668#M33736</guid>
      <dc:creator>Fugue</dc:creator>
      <dc:date>2013-12-18T22:35:38Z</dc:date>
    </item>
    <item>
      <title>Re: link  two tables - not exact match</title>
      <link>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175669#M33737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FYI -- your revised NAICS97 table is still incomplete: it does not have every possible NAICS code. However, that may be irrelevant depending on where you are pulling the data from and what you are trying to accomplish.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Dec 2013 23:16:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175669#M33737</guid>
      <dc:creator>Fugue</dc:creator>
      <dc:date>2013-12-18T23:16:28Z</dc:date>
    </item>
    <item>
      <title>Re: link  two tables - not exact match</title>
      <link>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175670#M33738</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FYI -- here is a link to a document which contains the concordance between I-O industry and NAICS. Go to printed page 39 (pdf page 21).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.bea.gov/scb/pdf/2002/12December/1202I-OAccounts2.pdf"&gt;http://www.bea.gov/scb/pdf/2002/12December/1202I-OAccounts2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This confirms my belief that the matching between your two files should be based on NAICS code.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Dec 2013 19:37:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/link-two-tables-not-exact-match/m-p/175670#M33738</guid>
      <dc:creator>Fugue</dc:creator>
      <dc:date>2013-12-19T19:37:31Z</dc:date>
    </item>
  </channel>
</rss>

