Also are there any records that have missing values for any of your class variables? The NWAY in proc summary doesn't create a combination of the class variables that include missing. So the totals of two different CLASS statements on the same value when the VAR variable is summed are likely to differ. The larger the difference the larger the difference in the number of records with missing class variables. Try using a dummy variable with a value of 1 for each record and compare the output. Use both proc summary and tabulate to compare the sums of the output data sets. A brief example of what I mean:   data junk; input c1 c2 c3 var1; datalines; 1 . 1 1 1 2 1 2 1 2 2 3 . 2 . 3 2 2 2 4 ; run; proc summary data=junk nway; class c1 c2 c3; var var1; output out= junk2 sum=; run; proc summary data=junk nway; class c1 c3; var var1; output out= junk3 sum=; run; proc means data=junk2 sum; title 'First group of class variables'; var var1; run; proc means data=junk3 sum; title 'Second group of class variables'; var var1; run; ... View more

Make the cell wider in Excel. It is not a SAS behavior causing this. ... View more

if score=2 then delete; would also work in a datastep. I might not actually delete them but when I go to the next step in analysis I would remove them using a dataset option. proc means data=new (where=(score ne 2)); for example. ... View more

It may be time to describe what you are attempting to accomplish overall. Many people coming from other programming backgrounds see SAS elements as behaving like another program might and often use an approach that can be accomplished much simpler than trying to translate another programming language approach. ... View more

Proc compare. Basic syntax Proc compare base=<datasetname> compare=<datasetname>; run; ... View more

Add Rows=2 after columns=1. The proportions may not look quite as you would like but they are one over the other. You may need to use other options to get the display area more to your needs as I think the default isn't very nice. An example for using dynamic variables, which is what you want, has an example in the online help named GSGREND1-Defining Dynamic Variables under SAMPLES for SAS/Graph. Basically you add a statement at the top of your template DYNAMIC <LIST OF VARIABLE NAMES>; Then define your graphic elements in terms of those variables. Then in your SGRENDER code you add a line that links your data variables to the dynamic ones in the template. Your final data call would look like one call to SGRENDER for each of those variables you wanted to process the same with the changes being to dataset (if other data set is needed) and the dynamic link. I hope this helps. ... View more

The error ERROR: You cannot reopen WORK.HOURLY_P.DATA for update access with member-level control because WORK.HOURLY_P.DATA is in use by you in resource environment SQL. usually means that you have the dataset WORK.HOURLY_p open somewhere. Possibly you have opened the table using Explorer or the Viewtable command. Or you have the columns view open in Explorer. The solution is to close whatever is using the dataset. In your case the nested reference to the same data set appears to be the offending procedure. Which is why the separation works, you only reference the set once. ... View more

Since the warning message says that the target is too short for specified source that makes me believe that you actually have values that are too large to be stored in 5 bytes, which would be 8 significant digits. Since you have a format associated of 11. that makes me believe that you are likely to have more digits. OR DI is using that format to assign the export length as a length of 6 is allows 11 significant digits. I would 1) verify that the largest value of the variable has 8 or fewer significant digits and 2) try changing the format before the export to 8. before the export and see if that changes the behavior. ... View more

If you are not doing arithmetic with a "number" such as account number it probably should not be a numeric but should be a string. Then you won't get the supprises when you try to format a long number into a shorter string. You have an account number with 10 significant digits and you tried to make it fit into 7. Similar, your branch number probably shouldn't be numeric either. Then the "problem" related to those goes back to whoever designs the original table to make sure they are big enough. But if you have codes that vary from 1234567890 to 12 you are going to have excess space for some. What do you get for your date values? Hard to trouble shoot without examples. ... View more

How do you define optimal in this sense? ... View more

Assuming you have created a table or dataset with the counts per association I would normally use procs format and freq. Instead of modifying query add as one way: proc format library=work; value members 0 - 100      = '   0 - 100 members' 101 - 500  = ' 101 - 500 members' 501 - 1000 = ' 501 - 1000 members'    1001 - 5000 = '1001 - 5000 members 5001 - high = '5001 or more members' ; run; /*assuming MemberCount holds the sum of members for each association, use your variable name*/ proc freq data=<your data set name>; table MemberCount ; format MemberCount members.; run; ... View more

Best to post what you attempted and any error log messages. ... View more