@Miracle - No problem, always happy to help! ... View more

If condition_start_date is a SAS datetime (the format wouldn't matter), you could use:   CREATE TABLE incl_crit1 AS SELECT *, condition_start_date BETWEEN "01JUL2010:00:00:00"dt and "30JUN2018:23:59:59"dt as incl_crit FROM cond_codes1;   If condition_start_date is character then you could get away with:   CREATE TABLE incl_crit1 AS SELECT *, substr(condition_start_date,1,10) BETWEEN "2010-07-01" and "2018-06-30" as incl_crit FROM cond_codes1; ... View more

Doesn't work is awful vague. Are there errors in the log?: Post the code and log in a code box opened with the {i} to maintain formatting of error messages. No output? Post any log in a code box. Unexpected output? Provide input data in the form of data step code pasted into a code box, the actual results and the expected results. Instructions here: https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-a-data-step-version-of-your-dat... will show how to turn an existing SAS data set into data step code that can be pasted into a forum code box using the {i} icon or attached as text to show exactly what you have and that we can test code against.     And you are using three tables. Perhaps you need to JOIN with the third table instead? ... View more

Looks like you are a victim of Microsoft's "stupid" quotes.  I typed John's grade into a MS Office app and then also pasted in the text from your message and Office decided that I didn't really want the simple ASCII character for a single quote character and replaced it with some other character that it interprets as looking something like what you might see in a type setting program instead in a computer program. So the normal single quote is ASCII code '27'x. In the WLATIN1 (or codepage 1252) the "stupid" quote is a "right single quotation mark" and is coded as '92'x.  IN UTF-8 is should appear as the multi-byte string 'E28099'x.   Not sure why SAS/Oracle are not automatically translating the character for you.  Hopefully one the links that others have provided will show how to get it to work.   If the only non 7bit ASCII codes your data has are these stupid quotes then I would recommend changing them all to normal single ('27'x) or double ('22'x) quotes.  However if your text fields also include more complex characters, like accented letters etc, then you need to get the encoding right.   You could try running SAS with the same LATIN1 (wlatin1, 1252) encoding and see if the characters come over from Oracle correctly. ... View more

Sounds like your top table could be compiled with something like this:   proc sql; create table polCounts as select County, Site, Pollutant, sum(matrix="Soil") as nbSoil, sum(matrix="Groundwater") as nbWater from myData group by County, Site, Pollutant; quit; where myTable would be your input data table with columns County, Site, Pollutant, and Matrix ("Soil" or "Groundwater")     replace sum(matrix="Soil") as nbSoil with sum(matrix="Soil") > 0 as nbSoil if you only want zeros and ones. ... View more

Thanks for replying @Miracle, but I cannot do that!   I need to correct it by applying the heteroscedasticity-consistent parameter estimates.   I can doit by using another PROC too. ... View more

I think the issue is on our drive, I have moved location and it now works fine. Thanks anyway. ... View more

if you can give an example( 5 to 10 rows) input dataset and output dataset, it will be very easy for help.       ... View more